adviceversion in jetty's bayeux impl

Hi,

I'm seeing weird behavior when opening two browser windows,
I see lots
of reconnect advice coming back to the second window and the
browser
kept sending reconnect messages to the server only to get
the same
reconnect advice.

A little debugging revealed that this piece of code in the
AbstractBayeux class

  if (client.getAdviceVersion()!=_adviceVersion)
   {
                    reply.put("advice",_advice);
                   
client.setAdviceVersion(_adviceVersion);
   }

always ran into the if block and sending the reconnect
advice back.

My questions are:

What does the adviceVersion do in this case? How to avoid
the infinite
quick looping in general?

I'd appreciate any help here, please.

-br


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cometd-dev" group.
To post to this group, send email to cometd-devgooglegroups.com
To unsubscribe from this group, send email to
cometd-dev-unsubscribegooglegroups.com
For more options, visit this group at http://grou
ps.google.com/group/cometd-dev

Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---

This is a feature not a bug 

If you run from two tabs, then you don't have enough
connections to
do long-polling from both of them.

So the java server uses the advice mechanism to make one the
second (and
third) implementations poll rather than long-poll.

cheers


bing wrote:
> Hi,
> 
> I'm seeing weird behavior when opening two browser
windows, I see lots
> of reconnect advice coming back to the second window
and the browser
> kept sending reconnect messages to the server only to
get the same
> reconnect advice.
> 
> A little debugging revealed that this piece of code in
the
> AbstractBayeux class
> 
>   if (client.getAdviceVersion()!=_adviceVersion)
>    {
>                    
reply.put("advice",_advice);
>                    
client.setAdviceVersion(_adviceVersion);
>    }
> 
> always ran into the if block and sending the reconnect
advice back.
> 
> My questions are:
> 
> What does the adviceVersion do in this case? How to
avoid the infinite
> quick looping in general?
> 
> I'd appreciate any help here, please.
> 
> -br
> 
> 
> > 
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cometd-dev" group.
To post to this group, send email to cometd-devgooglegroups.com
To unsubscribe from this group, send email to
cometd-dev-unsubscribegooglegroups.com
For more options, visit this group at http://grou
ps.google.com/group/cometd-dev

Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---

Greg,

Thanks for the explanation.

What does the adviceVersion mean? What duty does it handle?

The default _advise set the interval to 0, which caused the
browser to
keep sending reconnect request right after it receives the
response.
Should it be set to something longer like 1000?

thanks!


On 9月20日, 下午4时59分, Greg Wilkins <gregw.webt...gmail.com> wrote:
> This is a feature not a bug 
>
> If you run from two tabs, then you don't have enough
connections to
> do long-polling from both of them.
>
> So the java server uses the advice mechanism to make
one the second (and
> third) implementations poll rather than long-poll.
>
> cheers
>
> bing wrote:
> > Hi,
>
> > I'm seeing weird behavior when opening two browser
windows, I see lots
> > of reconnect advice coming back to the second
window and the browser
> > kept sending reconnect messages to the server only
to get the same
> > reconnect advice.
>
> > A little debugging revealed that this piece of
code in the
> > AbstractBayeux class
>
> >   if (client.getAdviceVersion()!=_adviceVersion)
> >    {
> >                    
reply.put("advice",_advice);
> >                    
client.setAdviceVersion(_adviceVersion);
> >    }
>
> > always ran into the if block and sending the
reconnect advice back.
>
> > My questions are:
>
> > What does the adviceVersion do in this case? How
to avoid the infinite
> > quick looping in general?
>
> > I'd appreciate any help here, please.
>
> > -br


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cometd-dev" group.
To post to this group, send email to cometd-devgooglegroups.com
To unsubscribe from this group, send email to
cometd-dev-unsubscribegooglegroups.com
For more options, visit this group at http://grou
ps.google.com/group/cometd-dev

Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---

you should be able to do this with the server side APIs.
Navigate to the Channel object and call .....  oh no API for
that :-(

Probably a need for that and other meta data.  I will add in
the next
week or so.

cheers



On Thu, 20 Sep 2007 23:56:57 -0700
bing <bing.rangmail.com> wrote:

> 
> Greg,
> 
> Thanks for the explanation.
> 
> What does the adviceVersion mean? What duty does it
handle?
> 
> The default _advise set the interval to 0, which caused
the browser to
> keep sending reconnect request right after it receives
the response.
> Should it be set to something longer like 1000?
> 
> thanks!
> 
> 
> On 9鏈�20鏃�, 涓嬪崍4鏃�59鍒�, Greg Wilkins
<gregw.webt...gmail.com> wrote:
> > This is a feature not a bug 
> >
> > If you run from two tabs, then you don't have
enough connections to
> > do long-polling from both of them.
> >
> > So the java server uses the advice mechanism to
make one the second
> > (and third) implementations poll rather than
long-poll.
> >
> > cheers
> >
> > bing wrote:
> > > Hi,
> >
> > > I'm seeing weird behavior when opening two
browser windows, I see
> > > lots of reconnect advice coming back to the
second window and the
> > > browser kept sending reconnect messages to
the server only to get
> > > the same reconnect advice.
> >
> > > A little debugging revealed that this piece
of code in the
> > > AbstractBayeux class
> >
> > >   if
(client.getAdviceVersion()!=_adviceVersion)
> > >    {
> > >                    
reply.put("advice",_advice);
> > >                    
client.setAdviceVersion(_adviceVersion);
> > >    }
> >
> > > always ran into the if block and sending the
reconnect advice
> > > back.
> >
> > > My questions are:
> >
> > > What does the adviceVersion do in this case?
How to avoid the
> > > infinite quick looping in general?
> >
> > > I'd appreciate any help here, please.
> >
> > > -br
> 
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cometd-dev" group.
To post to this group, send email to cometd-devgooglegroups.com
To unsubscribe from this group, send email to
cometd-dev-unsubscribegooglegroups.com
For more options, visit this group at http://grou
ps.google.com/group/cometd-dev

Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---