Please tell me if I can help write a JEP or other documentation. -- Dr. Klaus H. Wolf bluehands GmbH & Co.mmunication KG http://www.bluehands.de/people/hw +49 (0721) 16108 75
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Richard Dobson > Sent: Monday, July 29, 2002 3:17 PM > To: [EMAIL PROTECTED] > Subject: Re: General Redirect, was RE: [JDEV] 302 Redirect > > > Ok then this seems reasonable, > > Seeing as the use of 302 redirect is not set in stone yet, I suggest we > change it to this while we can and implement a different and better way of > telling a client to reconnect to a different server, similar to > the way msn > messenger does with its server transfer command, this also has > the advantage > that it can be done at any time not just as an error response to > a request. > > I suggest the following protocol: > > <iq type="set"> > <transfer xmlns="jabber:iq:srvxfr"> > <protocol>tcp</protocol> > <host>176.12.23.42</host> > <port>5222</port> > </transfer> > </iq> > > Can someone write a JEP up for me? Or have any information on how a JEP > should be written/styled? > Would you like to help Klaus and include your bit into it? > > Richard > > ----- Original Message ----- > From: "Klaus H. Wolf" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, July 29, 2002 12:38 PM > Subject: General Redirect, was RE: [JDEV] 302 Redirect > > > > OK, > > > > 1. reason: > > In my application I need to be able to redirect an IQ GET. The > client asks > > for a data object, but the data object might be somewhere else. > > > > 2. reason: > > I assume we agree, that Jabber is not only a presence Protocol, but a > > presence enabled messaging infrastructure with browsing capability. > Browsing > > is very important and will even grow. There might be other cases where > only > > the browse-target knows the real location of the data object. > The case is > > very similar to reasons for HTTP redirect. > > > > My idea was that the IQ result returns the entire new request (including > > id-attr) so that the client does not have to do more than just sending > this > > data. Even a potential request (which will usually be identified by the > > id-attr) is preserved and re-used. The redirect won't even > surface at the > > protocol engine level. It would be handled by lower layers of a Jabber > > protocol processor. > > > > -- > > Dr. Klaus H. Wolf > > bluehands GmbH & Co.mmunication KG > > http://www.bluehands.de/people/hw > > +49 (0721) 16108 75 > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > > > Richard Dobson > > > Sent: Saturday, July 27, 2002 11:17 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [JDEV] 302 Redirect > > > > > > > > > Why do you want to do redirects like this anyway? whats the point? > > > > > > Can you explain it to me/us please. > > > > > > Thanks > > > Richard > > > > > > ----- Original Message ----- > > > From: "Klaus H. Wolf" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Saturday, July 27, 2002 3:27 PM > > > Subject: RE: [JDEV] 302 Redirect > > > > > > > > > > Ok, right, I take a different one. > > > > Would you folks take note that WE might need a redirection > scheme for > IQ > > > > requests as we know it from HTTP, i.e. to be able to redirect the > entire > > > > request. Since IQ-get is used much (and more and more) like > > > HTTP GET this > > > > probably appropriate. > > > > > > > > -- > > > > Dr. Klaus H. Wolf > > > > bluehands GmbH & Co.mmunication KG > > > > http://www.bluehands.de/people/hw > > > > +49 (0721) 16108 75 > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf > Of > > > > > Richard Dobson > > > > > Sent: Saturday, July 27, 2002 2:47 PM > > > > > To: [EMAIL PROTECTED] > > > > > Subject: Re: [JDEV] 302 Redirect > > > > > > > > > > > > > > > Hi, > > > > > > > > > > My understanding is that a 302 redirect is supposed to be for > telling > > > the > > > > > client to re-connect to a specified server, for use in server farm > or > > > > > similar. > > > > > > > > > > E.g. as a response to an authentication the server may send: > > > > > > > > > > <iq type="error" id="authtag" [EMAIL PROTECTED] > from="server.com"> > > > > > <error code="302">jabber2.server.com:5269</error> > > > > > </iq> > > > > > > > > > > I dont think your use of 302 is correct, maybe your need > a different > > > error > > > > > code for your use. > > > > > > > > > > Richard > > > > > > > > > > ----- Original Message ----- > > > > > From: "Klaus H. Wolf" <[EMAIL PROTECTED]> > > > > > To: "Jdev@Jabber. Org" <[EMAIL PROTECTED]> > > > > > Sent: Friday, July 26, 2002 4:43 PM > > > > > Subject: [JDEV] 302 Redirect > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > can the 302 Redirect code be used for iq error responses? > > > > > > If yes: The saying is that the redirect JID is sent as CDATA of > > > > > the error > > > > > > tag, right? > > > > > > I propose to put the entire should-be request into the CDATA. > > > > > This allows > > > > > to > > > > > > change more than just the destination, i.e. the > namespace or more. > > > > > > > > > > > > Example : > > > > > > CLIENT: <iq id='5' type='get' to='user@server'><query > > > > > > xmlns='jabber:iq:xx'/></iq> > > > > > > SERVER: <iq id='5' type='error'> > > > > > > <error code='302'> > > > > > > <iq id='5' type='get' to='user@server'><query > > > > > > xmlns='storage:client:xx'/></iq> > > > > > > </error> > > > > > > </iq> > > > > > > > > > > > > It might be necessary to escape the embedded data. > > > > > > > > > > > > Opinions? > > > > > > > > > > > > -- > > > > > > Dr. Klaus H. Wolf > > > > > > bluehands GmbH & Co.mmunication KG > > > > > > http://www.bluehands.de/people/hw > > > > > > +49 (0721) 16108 75 > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > 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 > > > > > > > > > > > > > _______________________________________________ > > > 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 > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
