Thanks Greg.
As much as I would like to access the cometd directly, I
have a whole
web app deployed on a tomcat and running the jetty cometd
separately.
lighttpd work as a reverse proxy nicely and allow me to
bring all the
back end together.
So far what I have done is to set the keep-alive timeout on
the
lighttpd slightly longer than the cometd timeout and it's
working
fine. Hope it will hold up under heavy load.
BTW. I'm still using 0.94 version of the dojo.cometd.
I'll try the x-site again in my next free cycle.
Bing
On 12月17日, 下午2时56分, Greg Wilkins <gr... mortbay.com> wrote:
> bing wrote:
> > Hi,
>
> > I am experimenting with hosting the jetty cometd
server behind
> > lighttpd. Usually it's suggested that lighttpd
keep very short keep-
> > alive timeout for best output, sometime it even
goes to the extreme of
> > disabling keep-alive. In this case the dojo cometd
cannot use long-
> > polling at all. My application is a chat sort of
application and does
> > not require real time response. Is there a way I
force the client to
> > use the quick polling?
>
> You can configure the cometd servlet to be
"traditional" polling.
>
> The timeout is the wait on the server and the interval
is the
> wait on the client. Normally these are something like
>
> timeout=240000
> interval=0
>
> But if you configure them as
>
> timeout=0
> interval=30000
>
> then you will get polling every 30 seconds. Actually
I'm not 100%
> sure timeout=0 will work. But timeout=1 will. Please
test 0 and tell
> me if I need to fix that - as it should work.
>
> > What are your thoughts about the best way to
arrange jetty cometd and
> > reverse proxy to work together?
>
> Avoid having a proxy 
>
> make sure the host header is correct! ie the proxy has
not messed with it.
>
> > Another question about x-site.
>
> > It was my experience a while back that
cross-domain cometd was not as
> > stable as the same domain. The cross domain has
the ultimate advantage
> > of not occupying one of the two allowed
connections to the same domain
> > and that's why I'd like very much to get the
cross-site cometd working
> > for best user experience. Has there any progress
made in stablizing
> > the x-site feature?
>
> x-site is much better, but still a little way behind
same-site
> when it comes to error handling.
>
> Note that you have to configure the server to always
wakeup
> a poll so the response order is kept for the browser.
>
> cheers
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
|
