Changes between Initial Version and Version 1 of Ticket #9349, comment 31


Ignore:
Timestamp:
Sep 20, 2013, 11:00:05 AM (6 years ago)
Author:
infinity0
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9349, comment 31

    initial v1  
    1919
    2020The prefix/suffix ought to be opaque strings such that the separation is *unambiguous* (as opposed to a chain "a|b|c" where it's ambiguous where to split it into two). Then the matching algorithm remains as I described in the above post, but it's much easier to implement since each client/server transport has exactly one possible prefix-suffix separation.
     21
     22edit: to clarify, I understand that defining the suffix (as you do) to be "the last component" is unambiguous, but the nature of the chain syntax suggests extensions to this scheme (as what I did), but these extensions are not compatible with your model. So this is more of a "understandability for other people" rather than a semantic change.
     23
     24(on a side note, it *would* be possible to support the arbitrary-suffix syntax, if we recognised that certain protocols have a client/server directionality, but of course that is too complex for the time being. my point though, is that anything that suggests arbitrary composition / chaining of protocols will need to take this stuff into account, so it's best not to suggest chaining capabilities if we are far from being able to support them.)