All the negotiations == the PASS request :-) Once both sides are connected using PASS, the HTTP request/response commences, and from there on, everything's controlled using plain old HTTP (which is rediculously simple). Patching existing clients will be a piece of cake, and making new clients will be almost as easy.
- Dave Richard Dobson wrote: > > > On Wed, Feb 20, 2002 at 02:03:36PM -0000, Richard Dobson wrote: > > > > No ... I don't think you need 3 days to send some headers ... you just > > > have > > > > to preprend to all your outgoing connections "GET / HTTP/1.0\r\n\r\n" > and > > > to > > > > all incomming connections "HTTP/1.0 200 OK\r\n\r\n". I really can't > see > > > why > > > > you need 3 days to implement that. - Oh, sure ... you have to strip > that > > > > headers when you receive it ... 1 minute more to write the code for > that. > > > > > > What?? and you think that we be robust enough and compatible enough to > > > always work with all clients, somehow I doubt it. > > > > For most purposes this will be enough. And it can be easily extended > > when needed (and there is no need to invent new extensions). Will the > > new simple streaming protocol as extensible as HTTP? > > > > And this will work with existing Jabber clients. > > Are you sure it would be enough, wont the libraries that the clients are > built with be expecting all sorts of headers not just the request responses, > how extensible does the simple streaming protocol really need to be, all it > is supposed to be for is directly streaming a file p2p from one person to > another simply and easily, not having to deal with HTTP requests, and the > fact that the person might not immediately retrieve the file meaning that > you have to keep the port open indefinately until someone connects and > retrieves the file, which might not even be the real person, by doing this > streaming protocol you can do the negotiation and control over the xml > stream and it ends up being much easier and far more secure, im sure if you > needed to add any security into the HTTP example provided it would make it a > hell of a lot more complicated. > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
