Hi WG, this is again a request for some assistance/clarification.
I have a situation where an application can act as both a relay as well as a device in parallel. For example, it accepts incoming syslog messages and can relay them, but it also generates messages itself, e.g. by pulling them from the Windows event logs. My question is now about the role in the <iam> element. I assume I can handle this situation in two ways: #1 Two BEEP channels I open two channels to the remote peer. With one, I say <iam type='device>. With the other one, I say <iam type='relay'>. Depending on what is to be forwarded I use either the device or relay channel. #2 One BEEP channel, multiple <iam>s I open just one channel. Whenever I need to send something as a device, I issue a <iam type='device'> before sending the <entry> (if not already in "device mode"). Whenever I need to relay something, I issue an <iam type='relay'> before the entry (if not already in "relay mode"). I think both approaches are valid, but obviously #1 will be less-bandwidth-intense. Am I right with this? I am asking because there are so few implementations so far so you need to do "theoretical interop testing" ;) Any advise is appreciated. Rainer
