Might be worth considering to embed option a into option b, so that
common information can be factored out into the data structure but
transport specific or even out of band information can be sent in a
generic way
2 cents,
Ben
On 10/02/2015 09:36 PM, Jake Farrell wrote:
Agree with Roger, o
Agree with Roger, option B sounds like the preferable approach. Would
consider making this an option so people not interested in this type of
information would not have to incur any additional overhead for something
not in use
-Jake
On Fri, Oct 2, 2015 at 5:50 PM, Roger Meier wrote:
> Hi Jens
>
Hi Jens
Quoting Jens Geyer :
Hi all,
a frequent question is how a (typically server-side) event handler
could find out more about his counterpart, say the IP address or the
like. The common suggestion is that this is highly depending on the
transport (which is true) and therefore doomed
Hi all,
a frequent question is how a (typically server-side) event handler could find
out more about his counterpart, say the IP address or the like. The common
suggestion is that this is highly depending on the transport (which is true)
and therefore doomed to fail if anything changes at that
