yes, I agree!
we never know what's going on in the future...but we need inspiration ;-)
--roger
Quoting Rafael Garcia :
isn't this already sort of what the thrift http transport accomplishes? I
guess with websockets you can push from server to client, which you can't do
in Thrift.
On Fri, Se
isn't this already sort of what the thrift http transport accomplishes? I
guess with websockets you can push from server to client, which you can't do
in Thrift.
On Fri, Sep 10, 2010 at 4:11 AM, wrote:
> sorry, I forgot to tell about another hot topic for the future:
>
> http://dev.w3.org/html5/
sorry, I forgot to tell about another hot topic for the future:
http://dev.w3.org/html5/websockets/
Quoting ro...@bufferoverflow.ch:
Hi Rafael
please reply next time to the mailing list and not just to my
personal mail... that's Open Source;-)
The fastcgi thing I mentioned is not availa
Hi Rafael
please reply next time to the mailing list and not just to my personal
mail... that's Open Source;-)
The fastcgi thing I mentioned is not available right now, but this
should be a relatively easy step. Something like a
transport/TFastcgiServer.cpp very similar to other transport
Hi Rafael
here's my perspective:
1.javascript client in a production environment ?
I like to do so! As soon as I or some of my co-worker have time to fix
at least the map type bug (THRIFT-863) and do additional in deep tests
with the current implementation. That's just one of the reasons why I
The example javascript client in lib/js relies on a barebones http server
(httpd.java) compiled specifically for the ThriftTest service
(ThriftTest.thrift). I have a couple of questions:
1. Are people using the javascript client in a production environment?
2. If so, what's a typical configuratio
