Dave Cridland wrote: > On Thu Oct 23 11:48:09 2008, Dirk Meyer wrote: >> Hi, >> >> I had a strange discussion with a co-worker yesterday about the >> abuse of >> HTTP. Well, to make a long story short: >> http://www.tzi.de/~dmeyer/jingle-http.html >> >> This is a very early draft and only shows the very basic idea. What >> do >> you think? IMHO it could be useful. > > I think this would be useful to work on for a number of reasons, not > least because it gives me an excuse to suggest using it to run XMPP > over BOSH over HTTP over Jingle over XMPP over BOSH over HTTP over > Jingle over ... > > Come on, you were all thinking it.
Sure. And I can find a use case for HTTP over XMPP over BOSH. But if you want to use BOSH over XMPP over BOSH ... well, I guess I will be forced to report you to the protocol police because you abused at least two protocols. :) > Seriously, I can see lots of interesting, if slightly weird, use > cases for this. One interessting would be a reverse file transfer. Jingle filetransfer is a push mechanism: I want to send you a file and you can accept. With HTTP over XMPP it is the reverse. I may have a list of files you can pull from my client, maybe even a special bot only for file access. > There are slightly more if you introduce the concept of proxying, and > even more if one can figure out a way of encoding the Jid within the > URI, such that a browser might switch between HTTP/Jingle and > HTTP/TCP. That would be cool and I'm thinking about it. A method is needed to encode the full JID and the HTTP resource into one URI. But that is not that easy. Anyway, the current proposal is just a simple brain dump. More feedback (and use cases) welcome. ;) Dirk -- Students nowadays, complaining they only get 5MBs of disk space! In my day we were lucky if we had one file, and that was /dev/null.
