On 12/07/2015 07:26 PM, Jecel Assumpcao Jr. wrote:
Robert Withers wrote:
Ben, Huw, Todd and Sven, thank you all for your feedback! I suppose I could call the project "CryptOCaps" but for some reason I glommed onto mushroom as the name. Not grandiose and it is somewhat descriptive...a network of secure sessions, each one a mushroom. Ceps are highly valued. We can tag it for the catalog.
Though pretty old, the Mushroom Smalltalk computer was very well known at one time:
http://www.wolczko.com/mushroom/
Though one is a hardware project and yours is software, there is still the potential for some confusion.
-- Jecel
Oh dear, that's a potential naming conflict. Perhaps this is where the idea came from, as I have read about this Mushroom Project long ago. As this hardware project is not longer active, repurposing the name may be reasonable but I cannot say wityhout that authority. There are 2 layers, session & presentation, so perhaps 2 names are needed and the one project needs splitting. And there is the consensus issue. Perhaps I should use technical names and be done with it: SecureSession & CryptOCaps. Well, I will leave off changing again until agreed to names are established, as I don't know what to do about it, but I welcome suggestions...
Maelstrom, Mushroom, Crystalline & Phosphor, SecureSession & CryptOCaps, pther suggestions?
Robert
On Tue, Dec 8, 2015 at 8:25 AM, Robert Withers robert.w.withers@gmail.com wrote:
On 12/07/2015 07:26 PM, Jecel Assumpcao Jr. wrote:
Robert Withers wrote:
Ben, Huw, Todd and Sven, thank you all for your feedback! I suppose I could call the project "CryptOCaps" but for some reason I glommed onto mushroom as the name. Not grandiose and it is somewhat descriptive...a network of secure sessions, each one a mushroom. Ceps are highly valued. We can tag it for the catalog.
Though pretty old, the Mushroom Smalltalk computer was very well known at one time:
http://www.wolczko.com/mushroom/
Though one is a hardware project and yours is software, there is still the potential for some confusion.
-- Jecel
Oh dear, that's a potential naming conflict. Perhaps this is where the idea came from, as I have read about this Mushroom Project long ago. As this hardware project is not longer active, repurposing the name may be reasonable but I cannot say wityhout that authority. There are 2 layers, session & presentation, so perhaps 2 names are needed and the one project needs splitting. And there is the consensus issue. Perhaps I should use technical names and be done with it: SecureSession & CryptOCaps. Well, I will leave off changing again until agreed to names are established, as I don't know what to do about it, but I welcome suggestions...
Maelstrom, Mushroom, Crystalline & Phosphor, SecureSession & CryptOCaps, pther suggestions?
Grinding over your previous descriptions...
binary serialization to communicate over the wire
securewire --> 1900
secuawire --> 0
immunewire --> 2
wirymune --> 1 My overall favourite, if a little oblique ("wire immune").
tightwire --> 91200
substrate for distributed secure objects
obtransecua --> 0
obtransec --> 0 Equal favourite descriptive ("object transfer secure")
secuaobj --> 0
secushare --> 5880
kryptobj --> 4
kryptomesh --> 0 Equal favourite descriptive ("cryptographic mesh" of objects)
meshobsec --> 0
kryptnet --> 1220
cheers -ben
Thanks for doing this research, Ben. I checked 'kryptocap' with 363 results. If not Mushroom, I kinda like this one since it is an OCap system..
Cheers, Robert
On 12/08/2015 09:00 AM, Ben Coman wrote:
On Tue, Dec 8, 2015 at 8:25 AM, Robert Withers robert.w.withers@gmail.com wrote:
On 12/07/2015 07:26 PM, Jecel Assumpcao Jr. wrote:
Robert Withers wrote:
Ben, Huw, Todd and Sven, thank you all for your feedback! I suppose I could call the project "CryptOCaps" but for some reason I glommed onto mushroom as the name. Not grandiose and it is somewhat descriptive...a network of secure sessions, each one a mushroom. Ceps are highly valued. We can tag it for the catalog.
Though pretty old, the Mushroom Smalltalk computer was very well known at one time:
http://www.wolczko.com/mushroom/
Though one is a hardware project and yours is software, there is still the potential for some confusion.
-- Jecel
Oh dear, that's a potential naming conflict. Perhaps this is where the idea came from, as I have read about this Mushroom Project long ago. As this hardware project is not longer active, repurposing the name may be reasonable but I cannot say wityhout that authority. There are 2 layers, session & presentation, so perhaps 2 names are needed and the one project needs splitting. And there is the consensus issue. Perhaps I should use technical names and be done with it: SecureSession & CryptOCaps. Well, I will leave off changing again until agreed to names are established, as I don't know what to do about it, but I welcome suggestions...
Maelstrom, Mushroom, Crystalline & Phosphor, SecureSession & CryptOCaps, pther suggestions?
Grinding over your previous descriptions...
binary serialization to communicate over the wire
securewire --> 1900
secuawire --> 0
immunewire --> 2
wirymune --> 1 My overall favourite, if a little oblique ("wire immune").
tightwire --> 91200
substrate for distributed secure objects
obtransecua --> 0
obtransec --> 0 Equal favourite descriptive ("object transfer secure")
secuaobj --> 0
secushare --> 5880
kryptobj --> 4
kryptomesh --> 0 Equal favourite descriptive ("cryptographic mesh" of objects)
meshobsec --> 0
kryptnet --> 1220
cheers -ben
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.
----- Cheers, Sean -- View this message in context: http://forum.world.st/evolutions-of-squeakelib-crypto-Reed-Solomon-tp4864527... Sent from the Squeak - Dev mailing list archive at Nabble.com.
Branding and marketing connected to mythology, perhaps. I really don't know. There is something of value in a well-known name that brings inspiration; this is typically false inspiration, though, so I do see your point.
robert
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.
Cheers, Sean -- View this message in context: http://forum.world.st/evolutions-of-squeakelib-crypto-Reed-Solomon-tp4864527... Sent from the Squeak - Dev mailing list archive at Nabble.com.
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.
distributed object computer?
Cheers, Sean -- View this message in context: http://forum.world.st/evolutions-of-squeakelib-crypto-Reed-Solomon-tp4864527... Sent from the Squeak - Dev mailing list archive at Nabble.com.
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 robert.w.withers@gmail.com 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.
distributed object computer?
Cheers, Sean -- View this message in context: http://forum.world.st/evolutions-of-squeakelib-crypto-Reed-Solomon-tp4864527... Sent from the Squeak - Dev mailing list archive at Nabble.com.
-- . .. .. ^,^ robert
squeak-dev@lists.squeakfoundation.org
-
Ben Coman -
Huw Lloyd -
Robert Withers -
Sean P. DeNigris