[
https://issues.apache.org/jira/browse/THRIFT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443510#comment-13443510
]
Henrique Mendonca commented on THRIFT-1683:
-------------------------------------------
Thanks Richard,
as already discussed per mail, I was thinking to implement this using socket.io
which would probably facilitate the cross-language implementation for the
server side and offer some extra features for the client:
[https://github.com/learnboost/socket.io/wiki/] but yeah it's totally your call.
I won't have much time but I can try to give you a hand if you need, so keep in
touch!
ps.: as for NPAPI we could add a separated ticket for that, what do you think?
> Implement alternatives to Javascript Client side Transport protocol, just as
> NPAPI and WebSocket.
> -------------------------------------------------------------------------------------------------
>
> Key: THRIFT-1683
> URL: https://issues.apache.org/jira/browse/THRIFT-1683
> Project: Thrift
> Issue Type: Improvement
> Components: JavaScript - Library
> Affects Versions: 0.8, 0.9, 1.0, 1.1
> Environment: Client side development
> Reporter: Richard Elswick
> Labels: WebSocket, client, javascript, performance
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> The current Thrift.js Transport mechanism is only via AJAX. This should
> support the ability to choose the type as AJAX or WebSocket. An additional
> mechanism, which may make sense is a native call as well, through NPAPI or
> JSExtensions. This makes it useful for Embedded devices, which implement
> these methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
