You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Soheb Mahmood <so...@humboldt.co.uk> on 2011/10/26 10:25:29 UTC
wicketstuff-push examples working across browsers
Hello everyone,
I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
Many thanks,
Soheb
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Posted by Sebastian <no...@gmx.net>.
hi Soheb,
no problem. I gave it a try this morning on IE9 and it also failed with
the current push version in trunk. I just committed a change that makes
it work in IE.
https://github.com/wicketstuff/core/commit/3e09edf3e21fdb039cdb844e88653ccfdd33a4c4
Regards,
Seb
On 27.10.2011 15:58, Soheb Mahmood wrote:
> I just read my email again and I sounded really rude when asking my question. What I mean to ask was, out of curiousity, if you were trying to get the IE7 browser+ working?
>
> I'm really sorry if I've offended you or anyone. I'm very embarrassed by that tone in the email (it's not what I actually meant to say), and I really do appreciate your hard work and effort towards wicketstuff (as I have seen on git).
>
> Soheb
>
> ----- Original Message -----
> From: "Sebastian"<no...@gmx.net>
> To: users@wicket.apache.org
> Sent: Wednesday, 26 October, 2011 5:21:52 PM
> Subject: Re: wicketstuff-push examples working across browsers
>
> hi,
>
> cometd had a bug that affects websocket support in conjunction with
> chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd.
> We incorporated the changes (and fixed some other issues) in wicketstuff
> trunk. thus they will be available with the wicketstuff 1.5.2 release.
>
> Regards,
> Seb
>
> On 26.10.2011 10:25, Soheb Mahmood wrote:
>> Hello everyone,
>>
>> I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
>>
>> I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
>>
>> I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
>>
>> Many thanks,
>> Soheb
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Posted by Soheb Mahmood <so...@humboldt.co.uk>.
Hello Martin and Seb,
Just to drop an email to let you know how I'm doing so far, I've had a go yesterday, and to some extent, this morning at trying to get the master branch running, as I feel it is important to at least try and give feedback early as possible.
However, I've been struggling in trying to meet dependencies (it isn't anyone's fault but mine; I'm quite new to this and am doing this as a research project for our production application). I will try my best to actually get a wicketstuff-core snapshot, as well as a wicket snapshot and get the example running in IE.
Also, with Wicket 1.5.2 released recently, I assumed you'd get a stable version (even a RC) uploaded so at some point in the future I won't need to wrestle with snapshots any time soon.
Once again, many thanks for your time and effort.
Regards,
Soheb
----- Original Message -----
From: "Martin Grigorov" <mg...@apache.org>
To: users@wicket.apache.org
Sent: Thursday, 27 October, 2011 3:01:54 PM
Subject: Re: wicketstuff-push examples working across browsers
On Thu, Oct 27, 2011 at 3:58 PM, Soheb Mahmood <so...@humboldt.co.uk> wrote:
> I just read my email again and I sounded really rude when asking my question. What I mean to ask was, out of curiousity, if you were trying to get the IE7 browser+ working?
>
> I'm really sorry if I've offended you or anyone. I'm very embarrassed by that tone in the email (it's not what I actually meant to say), and I really do appreciate your hard work and effort towards wicketstuff (as I have seen on git).
Did you try the latest code from wicketstuff/core master branch ?
Maybe it already works on IE...
>
> Soheb
>
> ----- Original Message -----
> From: "Sebastian" <no...@gmx.net>
> To: users@wicket.apache.org
> Sent: Wednesday, 26 October, 2011 5:21:52 PM
> Subject: Re: wicketstuff-push examples working across browsers
>
> hi,
>
> cometd had a bug that affects websocket support in conjunction with
> chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd.
> We incorporated the changes (and fixed some other issues) in wicketstuff
> trunk. thus they will be available with the wicketstuff 1.5.2 release.
>
> Regards,
> Seb
>
> On 26.10.2011 10:25, Soheb Mahmood wrote:
>> Hello everyone,
>>
>> I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
>>
>> I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
>>
>> I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
>>
>> Many thanks,
>> Soheb
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Posted by Martin Grigorov <mg...@apache.org>.
On Thu, Oct 27, 2011 at 3:58 PM, Soheb Mahmood <so...@humboldt.co.uk> wrote:
> I just read my email again and I sounded really rude when asking my question. What I mean to ask was, out of curiousity, if you were trying to get the IE7 browser+ working?
>
> I'm really sorry if I've offended you or anyone. I'm very embarrassed by that tone in the email (it's not what I actually meant to say), and I really do appreciate your hard work and effort towards wicketstuff (as I have seen on git).
Did you try the latest code from wicketstuff/core master branch ?
Maybe it already works on IE...
>
> Soheb
>
> ----- Original Message -----
> From: "Sebastian" <no...@gmx.net>
> To: users@wicket.apache.org
> Sent: Wednesday, 26 October, 2011 5:21:52 PM
> Subject: Re: wicketstuff-push examples working across browsers
>
> hi,
>
> cometd had a bug that affects websocket support in conjunction with
> chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd.
> We incorporated the changes (and fixed some other issues) in wicketstuff
> trunk. thus they will be available with the wicketstuff 1.5.2 release.
>
> Regards,
> Seb
>
> On 26.10.2011 10:25, Soheb Mahmood wrote:
>> Hello everyone,
>>
>> I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
>>
>> I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
>>
>> I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
>>
>> Many thanks,
>> Soheb
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Posted by Soheb Mahmood <so...@humboldt.co.uk>.
Hello Seb,
Thanks for answering back to my email quickly. I'm glad to hear support for Chrome, but are you also supporting, at least trying to support IE7 and above?
Many thanks and regards,
Soheb
----- Original Message -----
From: "Sebastian" <no...@gmx.net>
To: users@wicket.apache.org
Sent: Wednesday, 26 October, 2011 5:21:52 PM
Subject: Re: wicketstuff-push examples working across browsers
hi,
cometd had a bug that affects websocket support in conjunction with
chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd.
We incorporated the changes (and fixed some other issues) in wicketstuff
trunk. thus they will be available with the wicketstuff 1.5.2 release.
Regards,
Seb
On 26.10.2011 10:25, Soheb Mahmood wrote:
> Hello everyone,
>
> I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
>
> I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
>
> I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
>
> Many thanks,
> Soheb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Posted by Soheb Mahmood <so...@humboldt.co.uk>.
I just read my email again and I sounded really rude when asking my question. What I mean to ask was, out of curiousity, if you were trying to get the IE7 browser+ working?
I'm really sorry if I've offended you or anyone. I'm very embarrassed by that tone in the email (it's not what I actually meant to say), and I really do appreciate your hard work and effort towards wicketstuff (as I have seen on git).
Soheb
----- Original Message -----
From: "Sebastian" <no...@gmx.net>
To: users@wicket.apache.org
Sent: Wednesday, 26 October, 2011 5:21:52 PM
Subject: Re: wicketstuff-push examples working across browsers
hi,
cometd had a bug that affects websocket support in conjunction with
chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd.
We incorporated the changes (and fixed some other issues) in wicketstuff
trunk. thus they will be available with the wicketstuff 1.5.2 release.
Regards,
Seb
On 26.10.2011 10:25, Soheb Mahmood wrote:
> Hello everyone,
>
> I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
>
> I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
>
> I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
>
> Many thanks,
> Soheb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: wicketstuff-push examples working across browsers
Posted by Sebastian <no...@gmx.net>.
hi,
cometd had a bug that affects websocket support in conjunction with
chrome browsers. It is fixed in the latest 1.4.0RC1 release of cometd.
We incorporated the changes (and fixed some other issues) in wicketstuff
trunk. thus they will be available with the wicketstuff 1.5.2 release.
Regards,
Seb
On 26.10.2011 10:25, Soheb Mahmood wrote:
> Hello everyone,
>
> I'm planning to use wicketstuff-core in an actual production environment, and to be more specific, I'm planning to use push-cometd. I'm currently using wicketstuff version 1.4.14 to match the current version of Wicket we are using in production.
>
> I got the example to run, and one of the things I wondered was what is the browser support aimed for push-cometd? So far, I can only get the cometd example working in Firefox and Opera, and there is a lack of support for Google Chrome 14.0.835.202 nor Internet Explorer 7. I can get the Wicket Timer example working, but the reason we are thinking of implementing comet into production is to minimize the request impact on our server, and with the Wicket Timer example, that uses TimerPushService, which if we wanted similar functionality, we could just use AjaxTimeoutBehavior instead. Even the Basic Cometd test doesn't work under IE7 and Chrome.
>
> I was wondering if you were aware of this, and if you had any suggestions to solve this cross-browser issue (at least from our end). It's also worth noting that I haven't modified the push-parent-jdk-1.6 folder contents at all.
>
> Many thanks,
> Soheb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org