[
https://issues.apache.org/jira/browse/THRIFT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691794#comment-13691794
]
Anoop Krishnan G commented on THRIFT-1683:
------------------------------------------
Socket.io is a good option as it supports multiple transport system , but
server side will be bit complex in that case so its better to go with native
websocket implementation first then migrate to the socket.io for multiple
transport support
> 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
