[JDEV] Re: OOB filetransfer negotiation

[johnston at megaepic.com]

A concept...

o On Server there is a CGI program
o ClientA wants to send a file to ClientB
o ClientA sends message to ClientB that says 'I wana
  send a file, fileX, connect here to Server's IP,
  TCP port 80'
o ClientB goes and does it
o Server returns in the http header OOB-Port: portX 
  where portX is some string
o Server does not finish sending headers - it just pauses
o Server and clientB stay connected
o ClientB sends ClientA a message and says, 'server says
  port is portX'
o ClientA posts to Server with a variable port = portX
  mime = mime/type and stream = base64 encoded file.
o Server finishes the http header to clientB giving the
  mime type, and then feeds clientB the stream from clientA
 
I know it's kinda silly, but it'd work and it would allow the web server to not temporarily store the data that's being sent like you need to do with the upload and reference method.

Mat.
 
On Thu, Aug 16, 2001 at 01:20:27PM -0500, temas wrote:
> Sebastiaan 'CBAS' Deckers wrote:
> 
> >>There are two workarounds that I know of to the firewall problem:
> >>(1) Sender uploads the file to a public server someplace, i.e. your
> >>storage area on your ISP account. Works best with FTP or WebDAV access.
> >>Then you send the receiver a URL to where the file got uploaded. I hear
> >>that some Jabber clients already support this.
> >>(2) Someone runs a public "relay server" that accepts connections from
> >>two machines that want to communicate, then relays socket traffic in
> >>both directions from one to the other. There is a prototype protocol and
> >>implementation at jabber.org (but I've lost the email that announced it.)
> >>