[JDEV] Re: jdev digest, Vol 1 #1054 - 13 msgs
shankar
lalshankar at svw.com
Sat Oct 6 00:18:37 CDT 2001
sasi,
going out in the afternoon. Will be back by 6pm. So just send me a mail
on the timings and location and I'll be there. No screw ups please.
Shankar.
----- Original Message -----
From: <jdev-request at jabber.org>
To: <jdev at jabber.org>
Sent: Friday, October 05, 2001 10:31 PM
Subject: jdev digest, Vol 1 #1054 - 13 msgs
> Send jdev mailing list submissions to
> jdev at jabber.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.jabber.org/listinfo/jdev
> or, via email, send a message with subject or body 'help' to
> jdev-request at jabber.org
>
> You can reach the person managing the list at
> jdev-admin at jabber.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of jdev digest..."
>
>
> Today's Topics:
>
> 1. RE: Namespace usage on server (Franck Mangin)
> 2. Jabber DevZone News - Federated Authentication with Jabber (Peter
Saint-Andre)
> 3. Jabber DevZone News - Python Jabber Server? (Peter Saint-Andre)
> 4. Jabber DevZone News - Jabber Everywhere (Jabber DevZone)
> 5. libjabber (=?iso-8859-1?Q?Henrik_H=E4rk=F6nen?=)
> 6. Jabber Server (Okan Bulut)
> 7. Jabber DevZone News - New Whiteboarding JIG (Jabber DevZone)
> 8. Single Sign on and stuff (Michael Hearn)
> 9. Re: Jabber Server (Peter Saint-Andre)
> 10. Re: SSL Yet Again (Chris Pile)
> 11. Re: Jabber Server (zariok)
> 12. Re: libjabber (Peter Saint-Andre)
> 13. Re: libjabber (Tom Jackson)
>
> --__--__--
>
> Message: 1
> Subject: RE: [JDEV] Namespace usage on server
> Date: Wed, 3 Oct 2001 14:42:41 -0700
> From: "Franck Mangin" <FMangin at facetime.com>
> To: <jdev at jabber.org>
> Reply-To: jdev at jabber.org
>
>
>
> > -----Original Message-----
> > From: Peter Saint-Andre [mailto:stpeter at jabber.org]
> > Sent: Wednesday, October 03, 2001 6:56 AM
> > To: 'jdev at jabber.org'
> > Subject: Re: [JDEV] Namespace usage on server
> >
> >
> > > <stream:stream to='jabber'
> > > xmlns:stream='http://etherx.jabber.org/streams'
> > > xmlns='jabber:client'>
> > > <iq id='A3' type='get'>
> >
> > vs.
> >
> > > <stream:stream to='jabber'
> > > xmlns:stream='http://etherx.jabber.org/streams'>
> > > <iq xmlns='jabber:client' id='A3' type='get'>
> >
> > The xmlns 'jabber:client' refers to the stream, not just any
> > old element
> > (e.g., your <iq/> element) within the stream, thus the error.
> > All streams
> > must be identified as jabber:client, jabber:component, or
> > jabber:server.
>
> From what I understand of XML namespaces, jabber:client defines a
> default namespace, which has no effect on the stream:stream element
> since the "stream" prefix explicitly puts it in the stream namespace.
>
> Franck Mangin
>
> --__--__--
>
> Message: 2
> Date: Thu, 4 Oct 2001 14:23:41 -0500 (CDT)
> From: Peter Saint-Andre <stpeter at jabber.org>
> To: jdev at jabber.org
> Subject: [JDEV] Jabber DevZone News - Federated Authentication with Jabber
> Reply-To: jdev at jabber.org
>
> FYI: I will continue to cross-post these items for about another week, at
> which time I will post them exclusively to news at jabber.org... </stpeter>
>
> ******
>
> Federated Authentication with Jabber
>
> The following was posted by stpeter at jabber.org via the Jabber DevZone web
> site (http://dev.jabber.org/):
>
> Dirk-Willem van Gulik has announced the availability of mod_auth_jabber,
> an Apache module that enables authentication against a Jabber server from
> within Apache (e.g., from any web page run on an Apache server). Dirk
> notes that it's not production quality code yet, but this is a great proof
> of concept for federated or third-party authentication using Jabber.
>
> http://jabber.org/?oid=2130
>
>
>
> --__--__--
>
> Message: 3
> Date: Thu, 4 Oct 2001 14:24:53 -0500 (CDT)
> From: Peter Saint-Andre <stpeter at jabber.org>
> To: jdev at jabber.org
> Subject: [JDEV] Jabber DevZone News - Python Jabber Server?
> Reply-To: jdev at jabber.org
>
> Python Jabber Server?
>
> The following was posted by stpeter at jabber.org via the Jabber DevZone web
> site (http://dev.jabber.org/):
>
> Daniel Bender has announced the existence of a project to write a
> Jabber server in Python, with obvious cross-platform implications. The
> project is called jserve and I'm sure it could use some contributors
> if any Python hackers are interested. :)
>
> http://jabber.org/?oid=2135
>
>
>
>
> --__--__--
>
> Message: 4
> Date: Thu, 4 Oct 2001 13:10:06 -0700
> To: jdev at jabber.org
> From: Jabber DevZone <webmaster at jabber.org>
> Subject: [JDEV] Jabber DevZone News - Jabber Everywhere
> Reply-To: jdev at jabber.org
>
> Jabber Everywhere
>
> The following was posted by stpeter at jabber.org via the Jabber DevZone web
site (http://dev.jabber.org/):
>
> Jabber, Inc. is now offering a free, 100-user version of its
> industrial-strength Jabber Communications Platform for evaluation and
> use by software developers, small businesses, ISPs, and anyone
> interested in Jabber. Entitled "JCP Express", the server is a
> pre-built binary that runs on Red Hat 7.1 and includes all the
> features of Jabber, Inc.'s commercial product, just for a limited
> number of users. To find out more or to download a copy, visit
> http://www.jabber.com/everywhere/.
>
> http://jabber.org/?oid=2136
>
> --__--__--
>
> Message: 5
> Date: Fri, 5 Oct 2001 13:30:17 +0300
> From: =?iso-8859-1?Q?Henrik_H=E4rk=F6nen?= <radix at st.jyu.fi>
> To: jdev at jabber.org
> Subject: [JDEV] libjabber
> Reply-To: jdev at jabber.org
>
> Hi everybody!
>
> Could someone help me where to find decent documentation about libjabber
> or some code examples to get me on the way to develop killer apps for
jabber.:)
> Just so annoying to try to figure out that <jabber/jabber.h>...
>
> --
> Henrik Härkönen <radix at st.jyu.fi> [ http://www.cc.jyu.fi/~radix ]
>
> --__--__--
>
> Message: 6
> From: "Okan Bulut" <okanbulut at hotmail.com>
> To: <jdev at jabber.org>
> Date: Fri, 5 Oct 2001 14:48:37 +0300
> Subject: [JDEV] Jabber Server
> Reply-To: jdev at jabber.org
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_002D_01C14DAC.D0F69860
> Content-Type: text/plain;
> charset="iso-8859-9"
> Content-Transfer-Encoding: quoted-printable
>
> I have been developing a jabber client using Jabber Server
>
> 1- If I use the client commercialy should I pay for that
> 2- Up to how many users will the server run properly ...
>
> thaks ...
>
> ------=_NextPart_000_002D_01C14DAC.D0F69860
> Content-Type: text/html;
> charset="iso-8859-9"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content=3D"text/html; charset=3Diso-8859-9" =
> http-equiv=3DContent-Type>
> <META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV><FONT face=3D"Arial TUR" size=3D2>I have been developing a jabber =
> client using=20
> Jabber Server</FONT></DIV>
> <DIV> </DIV>
> <DIV><FONT face=3D"Arial TUR" size=3D2>1- If I use the client =
> commercialy should I=20
> pay for that</FONT></DIV>
> <DIV><FONT face=3D"Arial TUR" size=3D2>2- Up to how many users will the =
> server run=20
> properly ...</FONT></DIV>
> <DIV> </DIV>
> <DIV><FONT face=3D"Arial TUR" size=3D2>thaks =
> ...</FONT></DIV></BODY></HTML>
>
> ------=_NextPart_000_002D_01C14DAC.D0F69860--
>
> --__--__--
>
> Message: 7
> Date: Fri, 5 Oct 2001 06:20:15 -0700
> To: jdev at jabber.org
> From: Jabber DevZone <webmaster at jabber.org>
> Subject: [JDEV] Jabber DevZone News - New Whiteboarding JIG
> Reply-To: jdev at jabber.org
>
> New Whiteboarding JIG
>
> The following was posted by stpeter at jabber.org via the Jabber DevZone web
site (http://dev.jabber.org/):
>
> The Jabber Council has just passed JEP-0010 and thereby put the
> Whiteboarding JIG into business. If you have an interest in the
> development of whiteboarding and other collaboration tools over
> Jabber, sign up for the mailing list at
> http://mailman.jabber.org/listinfo/whiteboard-jig.
>
> http://jabber.org/?oid=2139
>
> --__--__--
>
> Message: 8
> From: "Michael Hearn" <mhearn at mailandnews.com>
> To: <jdev at jabber.org>
> Date: Wed, 3 Oct 2001 22:10:55 +0100
> Subject: [JDEV] Single Sign on and stuff
> Reply-To: jdev at jabber.org
>
> Well, as there is still debate surrounding the JIG I think I'll just get
on
> with things here. At the end of the day, JIGs/JEPs are good but at the
> moment they are slowing this down. So - first issue: how would it work.
>
> Here is a doc I wrote a while ago, it details my current thinking on this.
> Comments please!
>
> Distributed Jabber Authentication
> by Mike Hearn (mhearn at neuk.net) Jabber: tweedledee at jabber.org
>
> ------------------------------------------------------------------------
> This document will assume knowledge of what network authentication is,
> and how Microsoft Passport operates.
>
> Jabber network authentication as outlined in this prelimary document
> will allow for the following things:
>
> * Authentication to arbitrary third party websites, without prior
> knowledge of that site.
> * Authentication to arbitrary services and servers, ie FTP servers,
> where both server and client are jabber aware
> * Authentication to services and servers for which the client is not
> jabber aware.
>
> _Website authentication_
>
> This involves using a special authentication website to allow web
> browsers to act as an authentication front end. It works like this:
>
> 1. User visits site A (mycompany.com) and wishes to login. They see
> one edit control, and a login button. They enter their network
> address into the edit, and click login/submit
> 2. Site A sends either a Jabber IQ or a SOAP message to the users
> server, that specifies the auth type (web), and a return URL.
> 3. Site B responds with a URL to the authentication website for that
> server. Each Jabber server has one, we'll assume it's
> *http://authenticate.jabber.org* here. The URL points to a CGI
> script that Site A will redirect to, for instance:
>
>
*http://authenticate.jabber.org/auth?token=120583asdbf5335sdfgy5767s*
> 4. At this address, the user is presented with a form which asks them
> to present credentials (probably a password, but could be anything
> - a certificate, iris scan, fingerprint data etc.) probably over a
> secure connection.
> 5. The user presents their credentials and submits. The
> authentication CGI logs into the users account to verify their
> identity, and if clear redirects the user to the URL specified in
> the original authencation request. At the same time, cookies are
> set on the authenicate.jabber.org domain, so if another site
> redirects to that site in future after Step 1, the login process
> is automatic.
> 6. Once returned to the original site A properly authenticated, Site
> A can set a cookie containing the username, so from now on when
> visiting that site you are automatically logged in.
>
> _Arbitrary services_
>
> We will use the example of a jabber aware FTP server and client for this
> section.
>
> 1. User connects to jabber-aware FTP server using jabber aware client
> 2. User gives client username and credentials (password, certificate,
> whatever)
> 3. User sends username to FTP server.
> 4. FTP server sends message to jabber server via either an IQ or SOAP
> asking for "service" authentication
> 5. Server responds with a token (random number), which the FTP server
> then sends to the client
> 6. FTP client hashes credentials with random number and sends to ftp
> server, which forwards this hash to the jabberd
> 7. Jabber server checks hashed credentials, and if clear sends
> message back to FTP server announcing this fact, or otherwise
> information about what went wrong.
> 8. User is now authenticated.
>
> _Arbitrary services when client is not Jabber aware_
>
> Often, a service may be Jabber aware, but the client is not. In this
> case, the client will prompt the user for a username and password for
> its own authentication system, but the user may wish to use Jabber
> authentication as supported by the server. In this case, Instant
> Messaging (IM) Authentication can be used.
>
> 1. User connects to jabber-aware FTP server with legacy client
> 2. Client prompts user for username and password
> 3. Client supplies Jabber network address and blank password
> 4. FTP server sends SOAP/IQ to server requesting "im" authentication.
> Server sends a message with embedded form to an active IM
> connection if one, otherwise authentication fails.
> 5. Users chat client receives message, for instance "Service
> 'SourceForge FTP' at 129.0.44.33 is requesting authentication.
> Confirm? YES NO" would be displayed in the chat client.
> 6. User clicks yes which triggers reply to server, which takes this
> message and replies to FTP service with a clear authentication.
> 7. FTP server has now authenticated the connection.
>
> This method utilises the fact that the user is probably running the chat
> client on the same machine as they are authenticating from.
>
> thanks -mike
> _______________________
> Michael Hearn
> mhearn at neuk.net
> Jabber (jabber.org) tweedledee at jabber.org
> ICQ# 34800568
>
>
> --__--__--
>
> Message: 9
> Date: Fri, 5 Oct 2001 09:05:13 -0500 (CDT)
> From: Peter Saint-Andre <stpeter at jabber.org>
> To: jdev at jabber.org
> Subject: Re: [JDEV] Jabber Server
> Reply-To: jdev at jabber.org
>
> > 1- If I use the client commercialy should I pay for that
>
> You mean pay jabber.org somehow? Not necessary.
>
> > 2- Up to how many users will the server run properly ...
>
> The most I've heard is 50,000 and that's with some tweaking. The
> next-generation server (development is just starting) will scale highers.
>
> Peter
>
>
> --__--__--
>
> Message: 10
> Date: Fri, 05 Oct 2001 16:02:41 +0100
> From: Chris Pile <cpile at snoogans.co.uk>
> To: jdev at jabber.org
> Subject: Re: [JDEV] SSL Yet Again
> Reply-To: jdev at jabber.org
>
> Top darts!
>
> Seems to work ok.
>
> I done the following:
>
> FreeBSD4.3
> - checked out jabber2 from the CVS
> - installed pth-1.4.0:
> "pkg-add -r
>
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.3-RELEASE/packages/devel/p
th-1.4.0.tgz"
> - installed gmake:
> "pkg-add -r
>
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.3-RELEASE/packages/devel/g
make-3.79.1.tgz"
> - "./configure --enable-ssl"
> - "gmake"
> compiled fine
> - customised jabber.xml
>
> Tested connecting with JabberIM 1.10.0.6 on W2K. Using the OpenSSL
> libraries from:
> http://download.sourceforge.net/jabbercom/jabbercom_openssl096.zip
>
> Here is some output.
>
> --
>
> su-2.05# netstat -an
> Active Internet connections (including servers)
> Proto Recv-Q Send-Q Local Address Foreign Address
> (state)
> tcp4 0 0 192.168.1.1.5223 192.168.1.2.3243
> ESTABLISHED
>
>
>
> Fri Oct 5 15:34:00 2001 mtq 8147100 leaving to pth
> Fri Oct 5 15:34:00 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:00 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:00 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio.c:377 _mio_accept calling accept on fd #8
> Fri Oct 5 15:34:01 2001 mio_ssl.c:230 SSL accepting socket with new
> session 80c7900
> Fri Oct 5 15:34:01 2001 mio_ssl.c:243 Accept blocked, returning
> Fri Oct 5 15:34:01 2001 mio.c:404 new socket accepted (fd: 14, ip:
> 192.168.1.2, port: 3134)
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio.c:755 MIO read from socket 14:
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio_ssl.c:145 Asked to read 8191 bytes from 14
> Fri Oct 5 15:34:01 2001 mio_ssl.c:159 Read blocked, returning
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio_ssl.c:145 Asked to read 8191 bytes from 14
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio_ssl.c:145 Asked to read 8191 bytes from 14
> Fri Oct 5 15:34:01 2001 mio.c:755 MIO read from socket 14:
> <stream:stream to="jabber.example.com" xmlns="jabber:client"
> xmlns:stream="http://etherx.jabber.org/streams">
> Fri Oct 5 15:34:01 2001 c2s [client.c:265] pthsock_client_read called
> with: m:808DA80 flag:2 arg:80906C0
> Fri Oct 5 15:34:01 2001 c2s [client.c:298] root received for 14
> Fri Oct 5 15:34:01 2001 c2s [client.c:303] Recieved connection to:
> jabber.example.com
> Fri Oct 5 15:34:01 2001 mio.c:1037 mio_write called on x: 0 buffer:
> <?xml version='1.0'?><stream:stream
> xmlns:stream='http://etherx.jabber.org/streams' id='3BBDC4D9'
> xmlns='jabber:client' from='jabber.example.com'>
> Fri Oct 5 15:34:01 2001 mio.c:276 write_dump writing data: <?xml
> version='1.0'?><stream:stream
> xmlns:stream='http://etherx.jabber.org/streams' id='3BBDC4D9'
> xmlns='jabber:client' from='jabber.example.com'>
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio_ssl.c:145 Asked to read 8191 bytes from 14
> Fri Oct 5 15:34:01 2001 mio.c:755 MIO read from socket 14: <iq
> type="get" id="JCOM_8"><query
> xmlns="jabber:iq:auth"><username>chris</username></query></iq>
> Fri Oct 5 15:34:01 2001 c2s [client.c:265] pthsock_client_read called
> with: m:808DA80 flag:3 arg:80906C0
> Fri Oct 5 15:34:01 2001 deliver.c:460 DELIVER 4:jabber.example.com
> <route type='auth' to='chris at jabber.example.com'
> from='14 at c2s/808DA80'><iq type='get' id='JCOM_8'><query
> xmlns='jabber:iq:auth'><username>chris</username></query></iq></route>
> Fri Oct 5 15:34:01 2001 deliver.c:651 delivering to instance
> 'sessions'
> Fri Oct 5 15:34:01 2001 deliver.c:83 (8090240)incoming packet <route
> type='auth' to='chris at jabber.example.com' from='14 at c2s/808DA80'><iq
> type='get' id='JCOM_8'><query
> xmlns='jabber:iq:auth'><username>chris</username></query></iq></route>
> Fri Oct 5 15:34:01 2001 util.c:92 config query auth
> Fri Oct 5 15:34:01 2001 mtq 8147000 entering from pth
> Fri Oct 5 15:34:01 2001 mtq 8147000 one call 815FC38
> Fri Oct 5 15:34:01 2001 authreg.c:52 auth request
> Fri Oct 5 15:34:01 2001 users.c:132
> js_user(chris at jabber.example.com,8166000)
> .
> .
> Fri Oct 5 15:34:01 2001 mio.c:604 mio while loop top
> Fri Oct 5 15:34:01 2001 mio.c:617 mio while loop, working
> Fri Oct 5 15:34:01 2001 mio_ssl.c:145 Asked to read 8191 bytes from 14
> Fri Oct 5 15:34:01 2001 mio.c:755 MIO read from socket 14: <iq
> id="vcard_356" type="get" to="chris at jabber.snoogans.co.uk/Jabber Instant
> Messenger"><query xmlns="vcard-temp"/></iq>
> .
> .
> Fri Oct 5 15:34:43 2001 mio.c:871 MIO is shutting down
> Fri Oct 5 15:34:43 2001 c2s [client.c:265] pthsock_client_read called
> with: m:808DA80 flag:4 arg:80906C0
> Fri Oct 5 15:34:43 2001 c2s [client.c:270] io_select Socket 14 close
> notification
> Fri Oct 5 15:34:43 2001 mio_ssl.c:132 SSL Cleanup for 80c7900
> Fri Oct 5 15:34:43 2001 mio.c:363 freed MIO socket
> Fri Oct 5 15:34:43 2001 mio.c:363 freed MIO socket
> Fri Oct 5 15:34:43 2001 mio.c:363 freed MIO socket
>
> --
>
> Looks like the whole mio loop works when "SSL_ERROR_WANT_*" occurs.
> Takes a few goes but gets there in the end. Let me know if you need
> anymore debug output, I only grabbed a few chunks that look relevant.
>
> I still want to do some more testing, but so far so good. Sorry for
> delay in response but hadn't checked the list for a few days.
>
>
> Thanks,
> Chris.
>
> temas wrote:
> >
> > Ok, I think we've got it this time. Current CVS works on the places I
> > could test that didn't work previously. I would love if people could
> > test this ASAP and let me know so it can be in 1.4.2.
> >
> > --temas
> >
>
------------------------------------------------------------------------
> > Part 1.2Type: application/pgp-signature
>
> --__--__--
>
> Message: 11
> Subject: Re: [JDEV] Jabber Server
> From: zariok <zariok at kiorisoft.com>
> To: jdev at jabber.org
> Date: 05 Oct 2001 11:03:13 -0500
> Reply-To: jdev at jabber.org
>
> Where has there been tests showing the .org jabberd will support 50G
> users?
>
>
>
> On Fri, 2001-10-05 at 09:05, Peter Saint-Andre wrote:
> > > 1- If I use the client commercialy should I pay for that
> >
> > You mean pay jabber.org somehow? Not necessary.
> >
> > > 2- Up to how many users will the server run properly ...
> >
> > The most I've heard is 50,000 and that's with some tweaking. The
> > next-generation server (development is just starting) will scale
highers.
> >
> > Peter
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
>
>
>
>
> --__--__--
>
> Message: 12
> Date: Fri, 5 Oct 2001 11:28:10 -0500 (CDT)
> From: Peter Saint-Andre <stpeter at jabber.org>
> To: jdev at jabber.org
> Subject: Re: [JDEV] libjabber
> Reply-To: jdev at jabber.org
>
> There is documentation for jabberd and libxode but not libjabber. What
> kind of killer apps do you want to create? Perhaps we can start from there
> and figure out what kind of docs you need. :)
>
> Peter
>
>
> On Fri, 5 Oct 2001, [iso-8859-1] Henrik Härkönen wrote:
>
> > Hi everybody!
> >
> > Could someone help me where to find decent documentation about libjabber
> > or some code examples to get me on the way to develop killer apps for
jabber.:)
> > Just so annoying to try to figure out that <jabber/jabber.h>...
> >
> > --
> > Henrik Härkönen <radix at st.jyu.fi> [ http://www.cc.jyu.fi/~radix ]
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> >
>
>
> --__--__--
>
> Message: 13
> Date: Fri, 05 Oct 2001 09:38:37 -0700
> From: Tom Jackson <tom at zmbh.com>
> Organization: DaraPro Security, Corp.
> To: jdev at jabber.org
> Subject: Re: [JDEV] libjabber
> Reply-To: jdev at jabber.org
>
> Henrik Härkönen wrote:
> >
> > Hi everybody!
> >
> > Could someone help me where to find decent documentation about libjabber
> > or some code examples to get me on the way to develop killer apps for
jabber.:)
> > Just so annoying to try to figure out that <jabber/jabber.h>...
> >
>
>
> I wrote a very simple client based on libjabber (jabtel). It shows the
> basics of getting the packet into the process, the rest is just
> application programming. It also has several impovements on libjabber
> (jab_poll & jab_recv), in that the select loop includes the stdin, and
> the client understands when the server dies or the user wants to quit
> (^D).
>
> You can find it at:
>
> http://zmbh.com/discussion/jabberclient/
>
> --Tom Jackson
>
>
> --__--__--
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
>
> End of jdev Digest
>
More information about the JDev
mailing list