Netty bayeux example doesn't work properly

[Tom Hastjarjanto]

Hi Dai Jun,
Thanks for your response, it now works in Firefox, in other browsers there
is still a(nother) bug. It throws an illegal charset exception. In
BayeuxDecoder it searches the http header ContentType for the charset of the
content, not all browsers send it ie. Chrome, Safari. Look for line 75. I do
not know what you plan to do in cases it is not send so I won't provide a
patch to "resolve" it. I guess you can either use it when its available and
just use the single argument decode function when it is not or you can just
ignore that information and always use the single argument function, really
up to you. Looking forward to new commits!

Good luck,

Tom

On Mon, Jul 27, 2009 at 11:36 AM, Dai Jun <guiwuu at gmail.com> wrote:

> Hi, Tom Hastjarjanto:
>
> Thanks a lot for your bug report and I am very excited about it, which
> is the first bug feedback from community. This bug is caused by a
> wrong client assignment of class ConnectRequest, assigning id property
> to clientId. I've already fix it as well as some spelling errors. You
> could check out the latest codes again and let me know if it still
> doesn't work.
>
> BTW, although the codec is not complete now, I am working on a big
> update with some
> features(
> http://guiwuu.blogspot.com/2009/07/bayeux4netty-report-5-new-journey.html
> ).
> Any feedback from you will help me a lot and I will be very
> appreciate.
>
> Best regards,
>
> Dai Jun or Danny Dai in English, http://guiwuu.googlepages.com
> GTalk: guiwuu at gmail.com | QQ: 93409048 | MSN: guiwuu at hotmail.com |
> Twitter: guiwuu
>
> On Mon, Jul 27, 2009 at 1:37 AM, Tom Hastjarjanto<tom at intellicode.nl>
> wrote:
> > Some additional information:
> > Post1 response:
> >
> >
> [{"channel":"/meta/handshake","supportedConnectionTypes":["long-polling"],"clientId":"5d529469-dc66-47b7-a2d8-b3e0d384e468"
> >
> >
> ,"minimumVersion":"1.0beta","successful":true,"version":"1.0beta","id":"0","advice":{"interval":0,"multiple-clients"
> >
> > :false,"reconnect":"retry"}}]
> >
> > Post2 response:
> >
> >
> [{"channel":"/meta/connect","clientId":"1","successful":false,"error":"401:clientId:Uknow
> > ClientId: 1"
> >
> > ,"id":"1","timestamp":"26-7-09
> >
> 17:34","advice":{"interval":0,"multiple-clients":false,"reconnect":"retry"
> >
> > }}]
> >
> > Post 3:
> >
> >
> [{"channel":"/meta/handshake","supportedConnectionTypes":["long-polling"],"clientId":"ccfbb57c-d868-4227-afb5-e2187626757a"
> >
> >
> ,"minimumVersion":"1.0beta","successful":true,"version":"1.0beta","id":"2","advice":{"interval":0,"multiple-clients"
> >
> > :false,"reconnect":"retry"}}]
> >
> > Post 4:
> >
> >
> [{"channel":"/meta/connect","clientId":"3","successful":false,"error":"401:clientId:Uknow
> > ClientId: 3"
> >
> > ,"id":"3","timestamp":"26-7-09
> >
> 17:35","advice":{"interval":0,"multiple-clients":false,"reconnect":"retry"
> >
> > }}]
> >
> > it seems it increments the clientid during handshake/connect phase
> > On Sun, Jul 26, 2009 at 6:57 PM, Tom Hastjarjanto <tom at intellicode.nl>
> > wrote:
> >>
> >> Hey guys,
> >> I was just playing with the latest version of the bayeux4netty source
> code
> >> from trunk, it doesn't seem to work properly. When I try to run it and
> >> insert my username it keeps sending a stream of post requests to
> >> http://localhost:port/cometd which respond with the wild web server
> >> response, When I look at the log messages it goes through the connect
> and
> >> handshake phase, sends some data and then starts the same cycle again, I
> >> don't know whether this is due dojo or the netty code, any pointers on
> what
> >> this might be?
> >> Thanks!
> >
> > _______________________________________________
> > netty-dev mailing list
> > netty-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/netty-dev
> >
> >
> _______________________________________________
> netty-dev mailing list
> netty-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-dev/attachments/20090728/2f4a4028/attachment.html