Sign In/My Account | View Cart  
advertisement

Article:
Beep BEEP!
Subject: Another Nit
Date: 2002-10-22 07:55:27
From: Ward Harold
Each peer sends its "greeting" message as soon as the connection is established, i.e., neither peer waits to receive the other's greeting before it sends its own greeting. So both of the following traces are valid:


S: <waiting for connection>
C: <open connection>
S: RPY 0 0 . 0 110
S: Content-Type: application/beep+xml
S:
S: <greeting>
S: <profile uri='http://iana.org/beep/TLS' />
S: </greeting>
S: END
C: RPY 0 0 . 0 52
C: Content-Type: application/beep+xml
C:
C: <greeting />
C: END


and


S: <waiting for connection>
C: <open connection>
C: RPY 0 0 . 0 52
C: Content-Type: application/beep+xml
C:
C: <greeting />
C: END
S: RPY 0 0 . 0 110
S: Content-Type: application/beep+xml
S:
S: <greeting>
S: <profile uri='http://iana.org/beep/TLS' />
S: </greeting>
S: END


Also, note that the "client" is free to advertise its own profiles, i.e., it could send something like:


<greeting>
<profile uri='http://my.org/QUOTESTREAM' />
</greeting>


to indicate that it supports the QUOTESTREAM profile. The server could then start a QUOTESTREAM channel to the client if it wanted to.

Previous Message Previous Message   Next Message Next Message

Full Text Titles Only Newest First

Sponsored By: