Re: Name change: Mushroom ( was Re: evolutions of squeakelib & crypto)
Name it by its defining responsibilities, not how it is implemented. It sounds like you have something that creates/establishes/maintains/manages CapTP sessions/connections.
Best,
Huw
On 18 December 2015 at 23:03, Robert Withers <[hidden email]> wrote:
On 12/18/2015 05:26 PM, Sean P. DeNigris wrote:
Robert Withers wrote
Perhaps I should use technical names and be done with it
Yes, please! I have used Squeak and Pharo almost every day for 6 years,
closely following the mailing lists, and still find the buffet of clever
project names baffling. Unless we're not trying to take over the world with
a particular project (like maybe Seaside, which could've blown Rails out of
the water given a little luck), I don't see what we gain in trade giving up
clarity.
What do you think would make a good name for what I am calling Mushroom, which was SqueakElib, but is really the 6th presentation layer above what are now SecureSession? It establishes a modified CapTP protocol (no searchpath & not all working). It is the presentation layer for distributed objects with promise pipelining : messages are sent to future results, and distributed result continuations. It's pretty neat. 5, 2. I am not sure what name accurately names this, what it does, where it is.
Locked
