Re: out_queue_push() CVS issue

> > Hi,
> >
> > when running rridxp-{client|server} using cvs versions of rridxp and
> > roadrunner I get the following debug message (RR_DEBUG=4:NET) from
> > within rr_tcp_connection_new():
> >
> > channel::out_queue_push_message enqueueing an unknown RPY, this can't be
> > right
> >
> > This seems to be introduced with the commit of rr on nov 8 (see
> > Changelog).
> >
> 
> This is not a bug in RoadRunner. The RRMessage api was slightly changed
> when another bug was fixed. And I forgot to update the RR/IDXP profile. A
> bugfix for the profile is now committed.
> 
> Thanks for spotting this!
> 
> Bug details:
>   RoadRunner now requires that all RRMessage derived message types has
>   to set "RR_MESSAGE(msg)->type" to the frame type (MSG, RPY, ERR...) in
>   the constructor. RoadRunner needs this info to correctly enqueue the message.
> 
Jonas,

thanks for your fast update! I just updated the cvs version and
recompiled and reinstalled first roadrunner and then idxp but the
message is still displayed.

Eventually you are referencing to a message saying

channel::out_queue_push type == unknown

which I also received in a idxp-tls client/server I'm trying to write
(along with some nasty GLIB errors ;). All this is now gone with the new
version.

Simply compile and run rridxp-{client|server} and look at the first
output lines (RR_DEBUG=4:NET) and you'll see what I mean.

Ciao,
Sandro
-- 
"Linux is like a wigwam: no windows, no gates ... apache inside!"

http://spoppi.home.pages.de/
http://www.lug-burghausen.org/