Yoav Nir y...@checkpoint.com wrote:
I also wonder if having four Shortcut Notify types might just be simpler
to
implement, rather than having another layer of type codes.
I'm also not clear why a Notify: it seems like it ought to be an entirely
normal payload type, cousin to
This is a really minor comment: you reserve 3-3 as unassigned
and 40K+ as private use. Why not make that boundary 49152, nice binary
multiple.
I also wonder if having four Shortcut Notify types might just be simpler to
implement, rather than having another layer of type codes.
I'm also not
On Jul 19, 2013, at 3:10 PM, Yaron Sheffer
yaronf.i...@gmail.commailto:yaronf.i...@gmail.com wrote:
Hi,
the comments below are focused on the protocol, rather than on its fit with our
requirements. So in a sense I'm jumping the gun here.
Summary
First, the document is very well written,
Hi,
the comments below are focused on the protocol, rather than on its
fit with our requirements. So in a sense I'm jumping the gun here.
Summary
First, the document is very well written, actually fun to read. It
presents a relatively simple solution
