Think about a name

17 views
Skip to first unread message

Jeff Lindsay

unread,
Dec 14, 2011, 6:52:40 PM12/14/11
to gser...@googlegroups.com
It's not a near term priority, but gservice may someday not be specific to gevent. In that case, it might be a good idea to have a name that isn't so tied to gevent. So just think about other names. Random terrible braindump:

pyservice
serviced
startstop

Obviously the "service model" is core to the design, so it would make sense if it could be incorporated into the name.

--
Jeff Lindsay
http://progrium.com

Sean McQuillan

unread,
Dec 14, 2011, 7:08:12 PM12/14/11
to gser...@googlegroups.com
My general naming model is to pick a random word that's unrelated to the project (e.g. parrot) then come up with stories about why it is that way =p.

Sean

Neuman Vong

unread,
Dec 14, 2011, 8:09:36 PM12/14/11
to gser...@googlegroups.com
ServiceX9000!!!1

On Wed, Dec 14, 2011 at 3:52 PM, Jeff Lindsay <prog...@gmail.com> wrote:



--
neuman

Chad Selph

unread,
Jan 6, 2012, 1:02:17 AM1/6/12
to gser...@googlegroups.com
Python/OTP

Neuman Vong

unread,
Jan 6, 2012, 1:04:26 AM1/6/12
to gser...@googlegroups.com
Cloud Python

On Thu, Jan 5, 2012 at 10:02 PM, Chad Selph <ch...@twilio.com> wrote:
Python/OTP



--
neuman

Jeff Lindsay

unread,
Feb 27, 2012, 1:36:34 AM2/27/12
to gservice
After lots of thinking and redesigning for the next major version of
gservice, I've been thinking about a new name as well.

My current thinking is based on trees. The tree-like structure of
services you build with gservice is fairly characteristic. Plus, I
like trees. But that's not a name.

In talking to people, lots of tree names have been proposed. Oak,
Juniper, Willow, Eucalyptus ... my current favorite is Ginkgo.
Although known as a herbal supplement (for memory and focus!), they're
actually really nice trees. It's also a very unique species and one of
the oldest. Unlike some of the others, it's not already used by a
framework or other popular open source system.

So, thoughts on Ginkgo?

-jeff

On Jan 5, 10:04 pm, Neuman Vong <neu...@twilio.com> wrote:
> Cloud Python
>
> On Thu, Jan 5, 2012 at 10:02 PM, Chad Selph <c...@twilio.com> wrote:
> > Python/OTP
>
> --
> neuman

Jeff Lindsay

unread,
Feb 27, 2012, 1:37:49 AM2/27/12
to gser...@googlegroups.com
And look how pretty the leaves are!
http://en.wikipedia.org/wiki/File:Ginkgo_Biloba_Leaves_-_Black_Background.jpg

Chad Etzel

unread,
Feb 27, 2012, 3:12:55 AM2/27/12
to gser...@googlegroups.com
+1 for Ginkgo, I like it.

Chad Selph

unread,
Feb 27, 2012, 3:01:28 PM2/27/12
to gser...@googlegroups.com
+1 Ginko

I think that now we're talking explicitly about Trees I think it would be beneficial to adopt some existing concepts about service trees.

In particular, I'm talking about "Supervisor Trees" in Erlang/OTP.  Basically, some services are supervisors, others are workers.  Supervisors only job is to know how to restart their child processes and follow different "restart strategies".

--
Chad Selph
Software Engineer

Jeff Lindsay

unread,
Feb 27, 2012, 3:06:30 PM2/27/12
to gser...@googlegroups.com
Supervisor trees have always been in my mind. In the last email about how Multiprocess would work, it very much applies the supervisor model. It will be interesting to think about the other cases. Is supervision about services or is it about the concurrency unit (greenlet, thread, process) that AsyncManager maintains? Is the restart strategy just an option for AsyncManager? Or do we implement it more at service level? Or have options for both? I think it will require actual use cases to figure it out. 

If you build an app, try and implement the supervisor tree if necessary and let's learn from that.
Reply all
Reply to author
Forward
0 new messages