Right, probably not the right place for the REST vs RPC debate(can't help myself sometimes).

I'm not sure I'm entirely clear where you are in this, do you have Legs up on some public repo where people can look at it.

------ really cannot help myself

As far as browsers go, orbited.org has a nice WebSocket tcp proxy thing going on.

Collin Miller
641 814 6585


On Jul 7, 2008, at 9:08 PM, "Bluebie, Jenna" <[EMAIL PROTECTED]> wrote:

But this is chat... the majority of it's usage is having messages pushed to you. Polling stinks, and the various ways of trying to force http to act like some kind of asyncronous push thing are all pretty crummy. There's no good reason not to use a tcp socket for this, though I agree it'd be easier to code a polling chat client. The only reason people use those weird polling and fake push things in real webpages is because browsers don't expose any Socket interface like flash does. It's just a work around for missing functionality, not a valuable design choice.

REST design principals are fine for some situations, but like XML, it all seems like a fad to me.

Besides which, half the point of this chat client is to find any problems or annoyances with my Legs library.

Reply via email to