There is a problem for which I don't currently have a solution. The
exchange.unbind command does not have an arguments field so
propagation of unbinds is problematic. One possibility (admittedly
ugly) is to use a field in the exchange.bind arguments to indicate
that a bind command is to be interpreted as an unbind for the purposes
of propagation.
I think you have found a bug in the spec... all commands where meant to have
a field table. There are probably 3 options
- we errata another method with the FT (not great)
- do something like you suggest . (ugly)
- map bind/unbind with the FT into qmf, and use QMF to negotiate the
dynamic routes.
Personally, I would use qmf.
Carl.
