(no subject)

Hi beepwg,

I have the following problem:
I implemented an application which starts several threads at the same time.
Everyone of these threads starts a channel. Messages are transmitted over
these parallel channels independently. I use ethereal for intercepting and
looking at the beep messages they were exchanged. 
But I see in some beep messages that the payload of these messages contains
an another beep message entirely. A section of ethereal looks like:

Blocks Extensible Exchange Protocol

      Header:
           Command: MSG
           Channel: 9
           Msgno: 1
           More: complete
           Seqno: 0
           Size: 555
            .
            .
            .
      Payload: (payload of MSG 9)END\r\nMSG  0 10 . 1980 214 ..........

Another example is like:

Blocks Extensible Exchange Protocol (no header section like above)

       Payload: MSG 11 1 . 0 600 \r\nContent-Type:
       Payload: application/xml\r\n\r\n (here comes the real payload)......


But my application works without any problems. There is no session
termination because of poorly-formed messages. Is this behavior  of beep normal? I
didn't see any section in rfc 3080 that refers to such problems.

Ingo 








-- 
GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++