Hi all! this week I have been busy digging various possibilities of using WebSockets + Wicket to render progress bar while fetching Freenet URIs.
* Why use websockets? To be able to push messages to the client without refreshing. * Why not long-polling? Because there is limit on persistent connections. * Why not continue using GWT? because its heavy and buggy. * What are the options? ** Wicket Native websocket (doesnt have fallback support) ** Wicket atmosphere integration (has fallback modes but is not the latest version of atmosphere integrated) * What do I want to do? I want to use Wicket native support and add ajax polling in case websockets are off. * What I want you to do? ** Let me know if you think there are reasons not to use websockets. ** if you think fallback mode (into ajax polling) is not necessary ** if you think using atmosphere is better than native websocket implementation of wicket Best pausb -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20120705/19ffd307/attachment.pgp>
