Shared Smalltalk (Secure Object Model)
Last updated at 12:08 am UTC on 1 November 2006
Please read the paper: SharedSmalltalk.
Then feel free to add comments below.
Rob Withers says:
This is a fantastically written paper. Please also look at Lex Spoon's Islands.
Also, I have published the EventualReference framework at Squeak-E. I have unpublished code, which builds a secure 168-bit peer2peer connection, called VatTP. The last step, over the next month or so will connect the EventualReference framework and VatTP, with what is known as CapTP, or Capability Transmission Protocol (or something :)).
squeak-e - the eventalReference framework will allow extension filters and services to be attached to support persistence, transactions, QoS, and teaTime.
CapTP will implement a carAndTrain distributed GC algorithm and provide support for eventual message sending.
in VatTP, the encryption and marshalling are pluggabe. The connection protocol negotiates with authentication, authorization, diffie-hellman key exchange, and protocol negotiation (compression, encryption, marshalling) and connections can be suspended and reconnect.
Please consider supporting this nascient framework, a 2 year effort of mine, to focus our efforts on a single capabilities model.
Below is a related but different topic. -ajh
Anthony,
Some of my questions for Open Croquet were at the 3D & social engineering level, rather than the code/object/method level.
Some examples...
Blocking another avatar's camera by creating a strategically positioned, small, opaque 3D object
Blocking another avatar's movement by creating a strategically positioned, small or invisible, solid 3D objects
Moving two portals together, to facing each other, so an avatar can’t get into the middle world from within either world of the two portals
Blocking another user’s 3D object selection mouse click by creating an invisible 3D object right in front of the user’s cursor to receive the click event instead of the visible 3D object
etc.
This has to do with creating new objects or moving objects already intended to be moved by their creators, rather than modifying another person’s object or methods as your system addresses.
Cheers,
Socinian
