[Siop-development] Who wants to look at the SIOP source code?

[Rapheal K. <ra...@ma...>]

  Folks who remember that they signed up to the siop-development mailing list,

  I have been going through something of an active development phase for SIOP 
lately.  I've been really happy with it.  If you all look at the wiki, you 
will see that there is something of a structure evolving from it.  I you 
check out the siop project from CVS, you can actually use the Ruby bindings 
to do... well it's not that useful by itself.

  In it's current state, you can create simple enterprise applications if you 
keep to a minimum your remote requests.  I wouldn't recommend it, of course, 
especially as there seem to be performance issues with SIOP running over 
sockets (the pipe based servers run nice and fast though).  You need to be 
prepared for that server to essentially run out of memory, of course, unless 
someone wants to implement the garbage collection mechanism.  This would 
consist of:

  1 - Implementing the "finalize" code for the proxy object.

  2 - Implementing the "release-reference" command.

  I know that nobody knows what I am talking about, but believe me, it makes 
sense.

  Otherwise, anyone up for a code review?  I know at least one of you is a 
right bastard about code criticism, and that kind of feedback is probably a 
good idea for now.

  - Rafe