[JDEV] One more thing about OOB

[Robert Temple]

I did look at HTTP to see if there was a natural fit for a client not
being able to connect to a server.  But of course there isn't because
these errors assume that a connection has been made to the server, since
its the server that is sending the error codes back.

I only picked 502 because I just saw the "Remote Server Error" next to 
it in the JPG and figured that was good enough for me until the jabber 
community could come up with something better.

I don't think 404 works, that is what the server should send back when
the client requests a resource that doesn't exist.  

I'm not even actually sure if its correct to have one client send
another client back an error in an iq.  Already the server sends back
a 503 error if the iq was sent to someone who is not online.  So maybe
all iq errors should come from the server.  Perhaps the client that
is a recipient of the oob should send a different type of error message,
embedded in a <iq type='result'... message.

Just to give you some background of what I'm trying to accomplish.
Obviously I'm working on file transport.  When a user wants to send
his buddy a file, his client starts a mini web server, creates a 
resource in the web server for the file and then sends the oob message.

If the recipient user okay's receiving of that file, then it tries
to connect to the sending person's computer.  If that connection fails
because they are behind different firewalls, etc, then I'd like to
sending client to know so that it can tell the user there was a problem
and ask the user if they want to put their file up on one of our servers
so that their buddy can download it from there instead.

-Robert


> -----Original Message-----
> From: Peter Saint-Andre [mailto:stpeter at jabber.org]
> Sent: Friday, December 01, 2000 2:58 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] One more thing about OOB
> 
> 
> Hi Robert,
> 
> I poked Jer about the error messages, too. :) Again we might want to
> look at RFC 2616 (ftp://ftp.isi.edu/in-notes/rfc2616.txt). Jer thought
> 401 sounded right but 502 didn't. If the recipient can't 
> connect to the
> URL, wouldn't we use 404? Maybe I'm misunderstanding exactly what you
> mean by that scenario.
> 
> RFC 2616 defines 502 as follows....
> 
> ******
> 
> 10.5.3 502 Bad Gateway
> 
>    The server, while acting as a gateway or proxy, received an invalid
>    response from the upstream server it accessed in attempting to
>    fulfill the request.
> 
> ******
> 
> Seems to me we'd probably want to stick close to the IETF standards
> here, which say that:
> 
>    Response status codes beginning with the digit "5" 
> indicate cases in
>    which the server is aware that it has erred or is incapable of
>    performing the request. 
> 
> It seems that by this scenario you mean something closer to 404, or
> perhaps 503.
> 
> Best,
> 
> Peter
> 
> --
> Peter Saint-Andre
> stpeter at jabber.org
> 
> > Robert Temple wrote:
> > 
> > One more thing about OOB iqs.  We need to figure out standard error
> > codes to use when a recipient is
> > unable to get a file for some reason.  Right now I'm going 
> to use 401
> > Unauthorized if the recipient
> > doesn't want to have the file sent to them.  And I'll use 502 Remote
> > Server Error if I the recipient cannot
> > connect to the URL that was sent though Jabber.
> > 
> > -Robert
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>