Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: RFC: A messaging kernel

From: petr:krenzelok:trz:cz at: 31-Dec-2002 9:30

Maarten Koopmans wrote:
> All, > > I am thinking/playing with the concept of a messaging kernel. > What is that? > > IMO, a messaging kernel would allow you to send a message to another > kernel, that dispatches it to the appropiate handler on arrival. > > So you would do: > > send-message some-uri [ some-message ] > > The receiving side would have been initialized with: > > message-kernel/add-message-type some-type some-handler > message-kernel/run ;enter the evnt loop, basicallyy a wait > > The rest is magic ;-) > > Now of course there is a lot of features to include: > - different transports (TCP, UDP, HTTP) > - security > - compression > - balancing > - persistent connections > > Think of it as the messaging counterpart of Rugby. > > Are there any things that you want to see included?
Hello Maarten, yes, something like that IS needed imo. I just would like to ask - why don't you try to contact DocKimbel to send you beta of Uniserve? Uniserve seems to be something like protocol multiplex engine - you have services installed, which use modules, e.g. httpd service, which can use CGI or fastCGI etc module. There is more to Uniserve than what I am able to describe here. What I currently lack with Uniserve is - client side of things .... I think that it should turn into P2P solution (and according to Doc, it hopefully will), as it currently lacks imo unified tracking of client side stuff also (I mean opened ports on client). Uniserve can be good competition to Python's Medusa and I think that later on, RT could decide to license it for SDK, as it can take Rebol networking one step further ... So - I would like to see community cooperation upon one as much as possible universal project, than later on deciding between two systems, while both of them lacking certain feature here or there ... -pekr-