On 05/07/12 22:42, Pouyan Zaxar wrote: > 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 is pushing necessary? What's wrong with having the browser client poll via normal AJAX? The WebSockets standard itself is in development. No wonder you are having trouble with libraries that implement it... > * 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 > > > > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl -- GPG: 4096R/5FBBDBCE https://github.com/infinity0 https://bitbucket.org/infinity0 https://launchpad.net/~infinity0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20120709/94515fdd/attachment.pgp>
