voila!, it worked!!! thanks Peter n David:)
-Ritu Quoting Peter Saint-Andre <[EMAIL PROTECTED]>: > And of course you need to have components and clients that understand > these namespaces. :) > > Peter > > -- > Peter Saint-Andre > email+jabber: [EMAIL PROTECTED] > weblog: http://www.saint-andre.com/blog/ > > On Wed, 17 Apr 2002, David Waite wrote: > > > Ritu Khetan wrote: > > > > >Hi Peter, > > > > > > I did go through the IETF draft and DJ\\\'s book, but > > >both of them do not discuss this in detail. I know that > > >jabber: cannot be used for custom namespaces. > > >I would like to have an example of declaring and > > >defining a custom namespace altogether. > > >Something like ritu:x:portfolio where I would like to > > >have a service to add stock information like: > > ><portfolio xmlns=ritu:x:portfolio jid=portfolio@localhost> > > > <stockname>ABC</stockname> > > > <price>12</price> > > > <date>20020417</date> > > ></portfolio> > > > > > That appears to be correct - you just put custom information in its own > > namespace (not prefixed with \"jabber:\"), and send it off wrapped in > > another packet, such as an IQ. > > > > -David Waite > > > > > > _______________________________________________ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
