Re: [DotGNU]Why DotGNU should go Jabber (was Re: Microsoft guru: Stamp out HTTP)

[Norbert Bollow]

> Also, the article references extending the SERVER. Maybe
> forking the code and/or rolling a library next in this proc,
> because Yet Another Daemon doesn't sound very appetizing,
> especially for RPC/whatever-protocol.

I don't think we need a jabberd of our own, as long as we need
the stand-alone jabberd only to handle cases where a process wants
to transmit-results-and-exit at a time when the recipient of
the results can't be reached directly.  I think that they'll be
very open to include in JOSS whatever patches are necessary to
make it meet our needs.  This won't be very significant changes
as that jabberd must only pass along out transmissions, the
jabberd doesn't need to really understand them.

Now that the licensing of JOSS has been fixed, I don't see any
point anymore in wanting to fork it.

This of course does not rule out the possibility of re-using
some code from JOSS whenever that may be convenient.

BTW, I envision the SEE daemon as acting as a Jabber client, not
as a Jabber server.

Greetings, Norbert.

-- 
A founder of the http://DotGNU.org project and Steering Committee member
Norbert Bollow, Weidlistr.18, CH-8624 Gruet   (near Zurich, Switzerland)
Tel +41 1 972 20 59       Fax +41 1 972 20 69      http://thinkcoach.com
List hosting with GNU Mailman on your own domain name   http://cisto.com