Advertisement announce/lookup failure in CoordinationAffix causes it to believe the server is a legacy node.

[monzum]

If the server is using the AFFIX framework and if it either fails to advertise the AFFIX string or if the client is unable to perform advertise lookup for the server node, the client believes that the server is a legacy node and will try to contact it using an empty stack. This could cause the message being sent and the message being received to be a mismatch and neither the server or client would know any better.

Example: Server uses AsciiShiftingAffix and successfully announces the AFFIX string using the CoordinationAffix. Client uses CoordinationAffix to do a lookup for the server's AFFIX string but gets an empty list back. Thus client believes that server is using a legacy connection and uses an empty stack. Due to the AFFIX stack being imbalanced on both sides, the application on the server side will receive a garbled message.

Is this the desired effect that we want?

[JustinCappos]

Definitely not.

Perhaps the server should essentially have a branching shim? In practice,
you'll want different connections (port, etc.) for legacy and non-legacy.

On Mon, Sep 30, 2013 at 11:41 AM, monzum [email protected] wrote:

If the server is using the AFFIX framework and if it either fails to
advertise the AFFIX string or if the client is unable to perform advertise
lookup for the server node, the client believes that the server is a legacy
node and will try to contact it using an empty stack. This could cause the
message being sent and the message being received to be a mismatch and
neither the server or client would know any better.

Example: Server uses AsciiShiftingAffix and successfully announces the
AFFIX string using the CoordinationAffix. Client uses CoordinationAffix to
do a lookup for the server's AFFIX string but gets an empty list back. Thus
client believes that server is using a legacy connection and uses an empty
stack. Due to the AFFIX stack being imbalanced on both sides, the
application on the server side will receive a garbled message.

Is this the desired effect that we want?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.