-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 6 Jan 2004 22:32, Nauman Khan wrote: > Thanks ! > > I liked the idea of making and loggin in as a component. Would you please > like to explain this thing a little bit more keeping in mind following > things
Here's some starting points for how to write components... Jabberd 1.4: http://www.jabber.org/jeps/jep-0114.html Jabberd 2.0: http://jabberd.jabberstudio.org/dev/docs/component.shtml In addition to this, a good component library will come with a working example or two. > 1- How will client mention in message that this is intended for the > component. The client will send a message to the component's JID. For instance, if the component's JID is "thingy.jabber.localhost", the client's message will be like this: <message to="thingy.jabber.localhost"> <body>Test message</body> </message> > 2- Will the component respond directly to the client or it will send > message to Server and server will automatically send response to the > client? All messages go through the server, but the component addresses the 'to' attribute of messages to the intended recipient. TX - -- 'Every sufficiently advanced technology is indistinguishable from magic' - Arthur C Clarke 'Every sufficiently advanced magic is indistinguishable from technology' - Tom Graves Email: Trejkaz Xaoza <[EMAIL PROTECTED]> Web site: http://xaoza.net/trejkaz/ Jabber ID: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/+ql9mifzwBMPxxoRAvmGAJ9j7kLDH6m7xKyCG3xi+8jwNgoKrQCffz8Y ip2C4M4NgHnV8atNsGFgoak= =Wg2q -----END PGP SIGNATURE----- _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
