3 ms·

I spent a year or so building my own comet server. Because I did that, I'm able to finely control every single element of it. I know in absolute detail how it w

by axod 17y ago

I spent a year or so building my own comet server. Because I did that, I'm able to finely control every single element of it. I know in absolute detail how it works, what sucks, what rocks, etc. Obviously you have to decide how important things are to your success, and decide if you should build it yourself, or use some existing code out there. For me, it was a no brainer decision. mod_comet is missing the point. Apache is the issue when using comet. Apache is what needs fixing/replacing. If Mibbit was using polling, my bandwidth bill would be through the roof.

jasonkester 17y ago
Sounds like we're in agreement then. If you want to use Comet today, you need to build something custom, and it will probably take a lot of time, but it will pay off as you describe in terms of flexibility.
- daleharvey 17y ago
  Im cetainly not, iserve, yaws and mochiweb are all "off the shelf" web servers that can handle comet pretty well. I cant believe erlang has the monopoly on lightweight web servers either.
  - jasonkester 17y ago
    Fair enough. Like you said elsewhere on this thread, we're down to defining "off the shelf" now, so I think we should probably call it a day. http://code.google.com/p/mochiweb/issues/detail?id=2 http://www.google.com/search?q=comet+site:http://yaws.hyber.org/ http://frihjul.net/iserve Those are the available docs for the technologies you mentioned. Yaws has some real documentation, but not for its Comet implementation. The others give you some source code and tell you to have fun. So yeah, it's right there on the shelf (how 'bout we settle on "perched on the edge of the shelf?") I'm just not smart enough (or motivated enough) to actually use any of it.
- axod 17y ago
  I still kinda disagree with your point though. There's nothing particularly unique to comet here. If you want to make anything the best it can be, you need to build it custom, and it will probably take a lot of time, but it will pay off...

by axod 17y ago

jasonkester 17y ago

Sounds like we're in agreement then. If you want to use Comet today, you need to build something custom, and it will probably take a lot of time, but it will pay off as you describe in terms of flexibility.

daleharvey 17y ago
Im cetainly not, iserve, yaws and mochiweb are all "off the shelf" web servers that can handle comet pretty well. I cant believe erlang has the monopoly on lightweight web servers either.
- jasonkester 17y ago
  Fair enough. Like you said elsewhere on this thread, we're down to defining "off the shelf" now, so I think we should probably call it a day. http://code.google.com/p/mochiweb/issues/detail?id=2 http://www.google.com/search?q=comet+site:http://yaws.hyber.org/ http://frihjul.net/iserve Those are the available docs for the technologies you mentioned. Yaws has some real documentation, but not for its Comet implementation. The others give you some source code and tell you to have fun. So yeah, it's right there on the shelf (how 'bout we settle on "perched on the edge of the shelf?") I'm just not smart enough (or motivated enough) to actually use any of it.
axod 17y ago
I still kinda disagree with your point though. There's nothing particularly unique to comet here. If you want to make anything the best it can be, you need to build it custom, and it will probably take a lot of time, but it will pay off...