You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@thrift.apache.org by Chi Vinh Le <cv...@chinet.info> on 2014/11/12 18:06:45 UTC

nodejs vs js implementation

Hi folks,

My goal is to use a javascript implementation for the browser and extend it with my specific needs.
Compatibilty with old browsers is important.

There seems to be a pull request for using the nodejs implementation in a browser using browserify
(https://github.com/apache/thrift/pull/251).

I am figuring out the differences between the nodejs and the normal js implementation.
There are quite some differences. Is there a specific design goals for the 2 implementations?
The nodejs implementation seems to be more comprehensive and better engineered.

I guess a browserified nodejs implementation will give compatibility issues with
old browsers am I right?

Anyone knows something that could help?

Chi

Re: nodejs vs js implementation

Posted by Randy Abernethy <ra...@apache.org>.
Hello Chi,

The Apache Thrift Node and Browser based javascript libs are the most
divergent in all of Thrift. While this is not exactly a good thing, I
think the historical influence leading to this is the async nature of
both platforms. I will take a look at the pull request you mentioned
and see if I can get it integrated. If you have other ideas for
improvements patches are always welcome.

Best,
Randy

On Wed, Nov 12, 2014 at 9:06 AM, Chi Vinh Le <cv...@chinet.info> wrote:
> Hi folks,
>
> My goal is to use a javascript implementation for the browser and extend it with my specific needs.
> Compatibilty with old browsers is important.
>
> There seems to be a pull request for using the nodejs implementation in a browser using browserify
> (https://github.com/apache/thrift/pull/251).
>
> I am figuring out the differences between the nodejs and the normal js implementation.
> There are quite some differences. Is there a specific design goals for the 2 implementations?
> The nodejs implementation seems to be more comprehensive and better engineered.
>
> I guess a browserified nodejs implementation will give compatibility issues with
> old browsers am I right?
>
> Anyone knows something that could help?
>
> Chi