donn at u.washington.edu
Mon Jun 5 19:02:14 CDT 2000
Quoth Deirdre Saoirse <deirdre at deirdre.net>:
| Speaking as an ex Be employee who was working on this very type of
| You might want to hold off on doing the BeOS client until the next
| networking stuff comes out.
| The newer networking (aka BONE) will require a lot less porting than the
| older style of Be's networking. You might be able to get in on the beta
| program, but the directions as far as coding were quite slim. I can answer
| some questions (I haven't been on #jabber in the last few days though).
I am really looking forward to the new network implementation, and
that's sure one of the hardest areas to deal with in ports, especially
But the present system shouldn't be a show stopper, I don't think.
I have been looking at the Jabber server (on UNIX), and for testing
I run a simple client that uses the Python interface (PyJabber),
on BeOS 4.5.2 PPC. The socket implementation was a little hairier
than something like POP, because you have to always be ready for
unsolicited data from the server, but that seems to me to be more
about threads and how to integrate a socket-bound thread with a
bunch of message dispatch threads, than about details of the socket
More information about the JDev