On Tue, 8 Jul 2008, Bluebie, Jenna wrote:
Hugh, thanks for your criticism and suggestions, but I have already made Legs, and it's quite stable. It's my personal dream networking tool. DRb is an interesting tool, but not a simple one, and from what I can tell, not an
Agreed, it's not simple. It has the merit that it has been out there for a while and has had the bugs beaten out of it.
especially interoperable one (for instance, with other programming environments, like flash, java, php... where my Legs uses a very simple protocol that can easily be implemented in other languages, and in some cases
Good point.
implementations already exist for the json-rpc 1.0 protocol.
[lots of good philosophical stuff trimmed] OK, then, usually the publish/subscribe model of Observable means your client classes have some kind of updata method, to which you can pass something to tell them what to do, what has changed. http://www.oreillynet.com/ruby/blog/2006/01/ruby_design_patterns_observer.html If you have access to "Head First Design Patterns" it is very clear on this one. This is leaving out DRb stuff. So the only question now is how does your present protocol permit the server to contact the client? Maybe each client needs to run its own server, somewhat more minimal than the main one. Tuplespaces may be still worth looking at, if only for the matching code. Hugh
