Thanks for the response Randy. I will try TBinaryProtocol. Regards, Gajanan
On Tue, Apr 26, 2016 at 7:23 PM, Randy Abernethy <[email protected]> wrote: > I think those two are a nice pair (C++ svr/JS client). Using browserify > some have used the Node lib to work with TBinaryProtocol in the browser. We > have some patches that add TBinaryProtocol to the Browser JS lib directly > but they stalled after we had some momentum around standardizing on one JS > lib and using browserify when folks wanted to use it on the front end. I > think at this point, adding TBinaryProtocol to the front end lib would be > worth doing. Then folks can go either way. Also would be nice to have a C++ > websocket impl so you could do C++/TBin/WebSock <=> JS/TBin/WebSock. We > have WebSocket on the front end but not in C++ (AFAIK) and on the JS side > we need to integrate one of the TBin patches hanging around. > > On Tue, Apr 26, 2016 at 2:40 AM, Gajanan H <[email protected]> wrote: > > > Hi, > > > > Is it advisable to use C++ thrift server and Javascript client? Are there > > any limitations due this combination? > > > > I understand that Thrift - Javascript only supports JSON protocol and > HTTP > > transport. C++ server does support JSON protocol over HTTP transport. I > > have tried a sample application and it works. > > > > I have multiple thrift services that are working with Binary protocol > over > > TSocket transport with both server and client implemented in C++. > > > > Regards, > > Gajanan > > >
