Potreban Javascript developer
Firma Teletrader d.o.o. trazi iskusnog Javascript developera za izmene i prosirenje Cometd Javascript biblioteke (http://www.cometd.org/). Posao je na honorarnoj osnovi.
Za detalje se javite na e-mail: [email protected].
Sledi kratki opis zadataka, kako biste mogli steci dojam o cemu se zapravo radi:
1. Adapt hidden-iframe transport to work with Cometd 1.0.1
We have a transport based on hidden-iframe technique that was written for beta version of Cometd Javscript client (version prior to official release v1.0.1 release). The transport relies on functionality provided by the Dojo Toolkit, as did the client prior to official release of v1.0.1.
The current version of Javascript Cometd client has a common layer where almost all functionality resides and very thin “bindings” for jQuery and Dojo frameworks. Prior to official release of v1.0.1, the client was refactored and a lot of internal parts were completely rewritten. Among other things, the transport “interface” and the way client chooses transport implementations were changed. The existing hidden-iframe transport is no longer compatible with the client.
The goal of the project is to adapt the hidden-iframe transport that we have to work with the latest version of Cometd client (v1.0.1).
General info about Bayeux, Cometd and the Javascript client: http://www.cometd.org/. The latest version of Cometd client can be found here: http://svn.cometd.com/trunk/cometd-javascript/. Support for custom transport was added as part of this issue here: http://bugs.cometd.org/browse/COMETD-17. The implementation of our hidden-iframe transport will be provided upon request.
2. Create a thin Cometd client that does not depend on Dojo or jQuery
We are looking into the possibility of implementing a very thin Cometd client that does not rely on Dojo or jQuery, but still provides basic functionality. The thin client needs to be fully Bayeux-compatible and has to be able to connect and exchange data with a Bayeux server (handshake, connect, subscribe, unsubscribe, disconnect). The client does not need to provide support for streaming or custom transports. The thin client is intended for mobile devices such as smart phones and needs to work on major mobile platforms.
 |  |
 |
