Hi,
it's just an idea but you could try to flush some kb of comments
before. Some browsers like Safari requires some kb of data at the
beginning of the stream to start the rendering.
And be sure you are not running some kind of service like Avast
WebShield which is buffering a http stream before rendering it.
--
Amaury aka dun4n
Le 23 mars 09 à 15:51, jewel_kader a écrit :
>
> Hi Jeanfrancois,
>
> Many thanks for your quick reply. I tried flushing comments before
> addCometHandler but it also seems not working.
>
> In IE, flushing comments results
> com.google.gwt.user.client.rpc.InvocationException at client side
> immediately.
>
> In FF, flushing comments does not comes to the client side
> immediately but
> it gets added with the first encoded response string sent from the
> server
> and eventually causes a error, since that comment makes the encoded
> response
> invalid.
>
> I also tried flushing a empty string (zero length) instead of a
> comment but
> it also didn't work in IE though it prevented the Firefox's error.
>
> I am new to grizzly and planning to write a online game server
> (Chess/Backgammon) using Grizzly and GWT but this IE error stopped
> everything. Can you please give me any other hints, so that I can try.
>
> --Jewel
>
>
> Jeanfrancois Arcand-2 wrote:
>>
>> Salut,
>>
>> jewel_kader wrote:
>>> Hi marcoflower,
>>>
>>> Does this long polling solution work in IE? I tried it in IE 6, 7,
>>> & 8. I
>>> got it not working in IE though no problem in Firefox.
>>
>> I will eventually look at it (apology for that) :-( To help, can you
>> flush some comments like before invoking addCometHandler(..):
>>
>>> // for IE
>>> writer.println("<!-- Comet is a programming technique that
>>> enables web servers to send data to the client without having any
>>> need
>>> for the client to request it. -->\n");
>>> writer.flush();
>>
>> I bet it will make it work. Keep me posted. If you can use
>> Wireshark or
>> ngrep to snoop the network that would help me as well.
>>
>> Thanks
>>
>> -- Jeanfrancois
>>
>>
>>>
>>> Thanks
>>>
>>> Jewel
>>>
>>>
>>> marcoflower wrote:
>>>> You can find the .war here http://www.marcofiore.it/GrizzlyTest.war
>>>> I'm using GlassFishV2 and Grizzly 1.0.19
>>>>
>>>> Thanks
>>>>
>>>> Marco
>>>>
>>>>
>>>> Jeanfrancois Arcand-2 wrote:
>>>>> Salut,
>>>>>
>>>>> marcoflower wrote:
>>>>>>> Just never call resumeCometHandler. That will means the
>>>>>>> connection
>>>>>>> will
>>>>>>> stay suspended (streaming mode) forever.
>>>>>> I tried to remove the resumeCometHandler call, but if I remove
>>>>>> it the
>>>>>> client
>>>>>> can't receive messages... I think is a specific GWT-RPC problem.
>>>>> Sorry for that. Can you send a test case (.war) that I can try?
>>>>> Which
>>>>> GlassFish or Grizzly version are you using?
>>>>>
>>>>> Thanks!
>>>>>
>>>>> -- Jeanfrancois
>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Marco
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/GWT-%2B-Comet-question-%28was-Re%3A--Jean-Francois-Arcand%27s-Blog--New-Comment-Posted-to-%27Building-GWT-Comet-based-web-app-using-Grizzly-Comet%27-tp21416392p22661728.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>