Well, first I had to getthe basics right (including the threading engine). I am thinking along these lines as well.
I think you will have a Rugby 'team' witha 'coach' or so.... --Maarten > Paul Tretter wrote: > >Hmmmm... why stop there... consider making rugby run in a cluster. Two > >rugby servers that can communication and exchange operational parameters > > on a per transaction (communication) basis. For example, send a request > > to the server and it goes to both servers. One will allow the other to > > process the request (the master rugby server) while the (slave rugby > > server) monitors the processing of the master server. If the master > > server communications fail then the slave rugby server processes the > > request. Maybe a new REBOL clustering transaction protocol and cluster > > server app. Damn to much brain storming in so little time. > > Well, another level I suggested to Maarten for Rugby was - Rebol > 'cluster - transparent propagation of functionality. Rebol clustering > servers would just exchange exposed functionality, so call to any of > them would do the work, but well, it needs probably some deep thinking > before implementation .... > > -pekr- > > >till next beer... > > > >Paul Tretter -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
