> > Hello,
> >
> > > > Simon how is the BNetEndpoint logger class going?. I would like
> > > > to
> > > > have
> > > > it to debug my P2P replys. Right now every time I send a P2P
> > > > message
> > > > my
> > > > chatting session is disconnected, I might be sending wrong
> > > > stuff.
> > > > I
> > > > would be great if the view would log in hex format also, to be
> > > > able
> > > > to
> > > > view the binary information of P2P messages.
> > >
> > > I am getting to the stage of integrating it. It seems to work for
> > > the
> > > DS handler, but no windows get created for the other
> > > BNetEndpoints.
> > > I
> > > couldn't really see where they were created though (I think they
> > > were
> > > not done with "new", which may be a problem).
> > >
> > > Is the P2P stuff sent as simple binary data then? Hmm, I can't
> > > think
> > > how to detect what is ASCII and what is binary - any ideas?
> > >
> > Actually all P2P messages have a binary header and footer. But the
> > data
> > could be either text or binary depending on the message. I think,
> > for
> > now it would be good to have an option to display the traffic
> > either
> > as
> > text or hex format. Or have both views like the hex viewer
> > DiskProbe
> > in BeOS.
I'll see what I can do.
> I forgot to tell you the other BNetEndpoints get created in the base
> class for the network handlers in MsnServerHandler, and they are
> created with new, but don't know why that would be a problem.
I tried a mulitple-file search for "BNetEndpoint", and only found the
one for the DS handler. I'll have a better look later, and try to get
something working by this afternoon.
> Daniel
Simon
|
