[
https://issues.apache.org/jira/browse/THRIFT-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443992#comment-13443992
]
Richard Elswick commented on THRIFT-1683:
-----------------------------------------
Glad you mentioned the socket.io here, Henrique. I forgot to mention it,
although I still have it open in a browser tab.
My intention was to get the structure moved away from being just dedicated to
one Transport method, then we can add others. WebSockets and AJAX use the same
Network Layer interface, but once you start talking about NPAPI or
JSExtensions, it gets dicey at best for how to apply the Thrift model to this
use case.
Yes, I would say a different ticket for each method make sense. Of course an
even better structure could be such that the network layer is separated as
well, so that say you wanted to send your Transport over a D-BUS internal
network or some other IPC. I am just not sure how this might apply here
though. Again, perhaps just a little bit out of scope of the original intent
for Thrift.
> 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
