Hi Emond, I don't really see the need to merge the code into one module and to remove he abstractions. There is indeed no need of the abstractions anymore but also they do not do any harm. The only need I can foresee is WebSocket 2.0 in JEE, but with the current speed of development of JEE this might be never.
I agree that the demo app could be merged to examples! I see that OpenShift started providing WildFly 10 so we can create examples8x.apache.wicket.org for 8.x. I'll do it in the coming days. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jan 13, 2017 at 8:56 PM, Emond Papegaaij <[email protected] > wrote: > Hi Martin, > > I noticed you didn't waste any time on this. Thanks for that! > > Do you think we should keep the separation between core and javax? I > don't think we will ever build an integration with a different api. > Perhaps we can also simplify the code afterwards, because this > abstraction over different apis is not needed anymore. > > Emond > > On Fri, Jan 13, 2017 at 3:02 PM, Martin Grigorov <[email protected]> > wrote: > > On Fri, Jan 13, 2017 at 10:46 AM, Emond Papegaaij < > > [email protected]> wrote: > > > >> Hi, > >> > >> I was wondering if we still need to support Tomcat 7.0 with native > >> websockets. > >> As far as I can see, Tomcat 8.0 and 8.5 both support JSR 356 and Tomcat > 7.0 > >> does not support Servlet 3.1, which is required for Wicket 8. > Therefore, I > >> think we should drop the wicket-native-websocket-tomcat module. Perhaps > we > >> should also merge javax into core and place the examples with the other > >> examples. > >> > >> > > Agreed! > > > > > >> With websockets becomming more and more standard, I'm not sure we still > >> need > >> wicket-atmosphere. wicket-native-websocket provides the same > functionallity > >> and more. Also, Atmosphere has a history of bugs and problems. I > wouldn't > >> recommend anyone to use it. > >> > > > > Agreed! > > > > > >> > >> Best regards, > >> Emond > >> > >> On maandag 31 oktober 2016 14:41:12 CET Martin Grigorov wrote: > >> > Hi, > >> > > >> > What other improvements do we need in 8.x/master before promoting it > to > >> > 8.0.0 final ? > >> > > >> > At https://cwiki.apache.org/confluence/display/WICKET/ > >> Ideas+for+Wicket+8.0 > >> > we still have: > >> > > >> > - new DateTime APIs for wicket-datetime *WICKET-6105 > >> > <https://issues.apache.org/jira/browse/WICKET-6105>* - I'll give this > >> one > >> > more try but the problem is that I don't believe this is the proper > way > >> and > >> > this demotivates me. > >> > If someone else wants to give it a try - please assign it to yourself! > >> > > >> > - Better SEO for stateful pages - the only way I see this is by using > >> > ServiceWorker to add the pageId as a request header to all requests > >> (normal > >> > & Ajax) > >> > > >> > > >> > Recently I wondered whether Redux.js could be in use for Wicket. > >> > I don't have much experience with it, but both React and AngularJs > >> > communities use it to manage the state for their components. > >> > There are some Java impls, even a standard is coming: > >> > https://github.com/jvm-redux/jvm-redux-api > >> > > >> > What else ? > >> > > >> > Martin Grigorov > >> > Wicket Training and Consulting > >> > https://twitter.com/mtgrigorov > >> > >> > >> >
