4 ms·
Find a good way to have an asynchronous feed back from a web server to a web client, a true general purpose "push" protocol as an extension of HTTP. Hey you ca
by joe24pack 19y ago
Find a good way to have an asynchronous feed back from a web server to a web client, a true general purpose "push" protocol as an extension of HTTP. Hey you can even call it HTTP2W or HTTP2HTTP. Of course you'll have to come up with not only the protocol definition but also a reference implementation for both the client and the server. Sounds like fun, eh?
- mixmax 19y agoSounds like it will be impossible to make money.
- joe24pack 19y agoHey, I like to make a buck just like the next guy, but it still sounds like a neat thing to work on. I'm sure you could find a way to charge someone something after developing this.
- mixmax 19y agoWell look at comet, django, rails, scriptalicious, and just about all other frameworks or neat pieces of code that developers can use to do something better. None of them make any money.
- technoguyrob 19y agoAlready exists: http://en.wikipedia.org/wiki/Comet_%28programming%29 http://en.wikipedia.org/wiki/Comet_%28programming%29
- joe24pack 19y agoThanks, I'm aware of Comet. Not exactly what I meant, in Comet the connection stays open after being initiated by the client. I'm looking for something where the interaction is first client-to-server, then client registers a "callback" address and port that it will listen to. This would be followed by a server-to-client call where the server will send updates/events to client as they happen, the client then decides what to do with those events. I want to avoid a persistent connection, and either the "heartbeat" client requests or other forms of polling by the client. The interaction that I'm looking for is more akin to a P2P sort of model.
- xirium 19y agoI believe that YCombinator also declined to fund this idea ( http://news.ycombinator.com/item?id=95931 http://news.ycombinator.com/item?id=95931 ), which demonstrates how hard it is to have a good idea.