Web sockets support clarification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

we are currently using Wicket 6.17 and use a version of Atmosphere jar libraries (not the wicket version). Its never been great and have had lots of production issues with it. I'm looking to replace it with straight web sockets as the fall back long polling etc we never could get to work.

Looking at wicket documentation around web sockets am I correct in the following:

If the servlet container supports JSR356 (ie. tomcat 8) we only need to use wicket-native-websocket which comprises of wicket-native-websocket-core  and wicket-native-websocket-native?

If we are on non JSR356 containers we need to use wicket-native-websocket-jetty/wicket-native-websocket-tomcat ?

Is wicket-native-websocket production ready?
Is there any compatibility issues with Wicket 6.17?


Finally on a separate note where can I find a 'Whats new in Wicket 7.0' - specifically new features etc? The change log is not very clear for me.

Many thanks

[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux