Did you've found a sollution for your case?
And, did you already take a look to GWTEventService? :)
On 27 apr, 06:53, "davidst...@gmail.com" wrote:
> I mean this : getThreadLocalRequest().getSession().getId()
> gives me the same id for two different clients that are opened.
> Someone told me th
Uggh - I don't bother with that. There's too many problems (at least
anecdotally from 3rd parties - I've never used it myself). I think it's
because there's no good overview describing how it works & what the various
limitations are. Thus when you integrate with GWT, you can encounter
situations
I mean this : getThreadLocalRequest().getSession().getId()
gives me the same id for two different clients that are opened.
Someone told me that maybe two browsers share a cookie cache/address
space
and because of that they see the same cookie.
I googled this theme about two weeks but i did not fin
On Sun, Apr 26, 2009 at 3:29 PM, davidst...@gmail.com
wrote:
>
> > Are you sure you're not doing a notify? Maybe you actually receive an
> > event? InterruptedException (from memory, haven't looked at the javadoc)
> > get's called when wait times out - if you call notify, it'll wake up the
> > t
> Are you sure you're not doing a notify? Maybe you actually receive an
> event? InterruptedException (from memory, haven't looked at the javadoc)
> get's called when wait times out - if you call notify, it'll wake up the
> thread normally.
That's exactly what i do there, notifying.
Forgive my
On Thu, Apr 23, 2009 at 2:05 PM, davidst...@gmail.com
wrote:
>
> I tested both FF and IE6 . I'm pretty surprised too of the results, so
> I'm still searching the problem.
>
> >Are you calling getEvents (the one
> > that sends of the request to the server) on the client-side more than
> once?
>
> N
Thanks Rvanlaak. I'll check those links.
On Apr 23, 3:52 pm, Rvanlaak wrote:
> For a chat app the Comet principal is needed. I've had the same
> problem, so I would really advise you to look at the GWTEventService
> library. That lib supports your needs out of the box, and is GWT 1.6.4
> compat
I tested both FF and IE6 . I'm pretty surprised too of the results, so
I'm still searching the problem.
>Are you calling getEvents (the one
> that sends of the request to the server) on the client-side more than once?
No, i checked it after you said that two requests is the maximum.
I call the g
I tested both FF and IE6 . I'm pretty surprised too of the results, so
I'm
still searching the problem.
>Are you calling getEvents (the one
> that sends of the request to the server) on the client-side more than once?
Yes, i checked it after you said that two requests is the maximum.
I call the
For a chat app the Comet principal is needed. I've had the same
problem, so I would really advise you to look at the GWTEventService
library. That lib supports your needs out of the box, and is GWT 1.6.4
compatible. Start using the lib is kinda tough, but you'll don't
regret it!
Take a look at ht
Seriously doubt it's a hosted mode mode issue. Which browser did you test
web-mode with? Hosted mode actually launches a version of IE6, so using FF
or IE7 may present different issues (for instance they might have a raised
AJAX connection limit)
The issue is purely on the client side. Are you
Well, it really looks like a bug, cause when i
compile it to browser it works properly ( meanwhile ).
Thanks for your answers.
On Apr 23, 10:05 am, Salvador Diaz wrote:
> As Vitali said, there are some common pitfalls when trying to
> implement something along the lines of whatyou're trying
As Vitali said, there are some common pitfalls when trying to
implement something along the lines of whatyou're trying to do.
There have been plenty of discussions related to chat implementations
and server-push. You might want to look at this docs:
http://docs.codehaus.org/display/JETTY/GWT+RPC+E
I open two clients, and trying to send a message from one to another.
So i have two requests hanging on server's side, and the third one
trying to send the message.
the server side is like this :
@Override
public ArrayList getEvents( Integer sessionId )
{
U
Most browsers only support 2 outstanding AJAX events - that may be what you
are running into. Without knowing what other calls you make, I cannot make
a recommendation.
One thing that does come to mind is that I hope you only call getEvents once
on startup.
On Wed, Apr 22, 2009 at 4:47 PM, david
Hi.
I'm trying to implement chat on my GWT app. So client has getEvents()
function implemented like this :
public void getEvents( )
{
networkSvc.getEvents(
new AsyncCallback< ArrayList >()
{
public void
16 matches
Mail list logo
