Tent v0.1 released

Posted Sep 21, 2012 22:37 UTC (Fri) by Cyberax (✭ supporter ✭, #52523)
In reply to: Tent v0.1 released by job
Parent article: Tent v0.1 released

HTTP is a nice protocol. It doesn't require reinventing the wheel and it has lots of nice infrastructure built around it (caching proxies, load balancers, etc.). So deal with it.

JSON is just a nice and easy serialization format.

Tent v0.1 released

Posted Sep 22, 2012 10:07 UTC (Sat) by job (guest, #670) [Link] (2 responses)

But yes it does. That's the whole problem with it. HTTP is not a pubsub protocol.

Designing one that works over HTTP requires a whole lot of wheel reinvention, because of its shortlivedness, statelessness etc. It's just not a suitable transport.

The "nice" infrastructure around it is part of the problem. Caching proxies cause no end of problems when pushing state around.

Tent v0.1 released

Posted Sep 22, 2012 13:47 UTC (Sat) by AlexHudson (guest, #41828) [Link]

HTTP/1.0 in a narrow sense, sure. Pipelining wasn't added long after and server push was in there very early on, now we have better systems like websockets but the principle is the same.

Caching proxies don't cause any problem so long as the system is used correctly, and HATEOAS-style services work well and benefit from the caching.

Even incompatible protocols like SIP borrow heavily from it. It's a fine technical choice.

Tent v0.1 released

Posted Sep 22, 2012 18:49 UTC (Sat) by Cyberax (✭ supporter ✭, #52523) [Link]

Which is great! Internet in itself is not a pubsub media, it's a stateless transfer media with unreliable connectivity.

I've seen tons of protocols that just use TCP and happily build very statefull systems on top of it. And of course, they usually can't survive broken connections.