Thanks for your answers. Please, see below. Le 10/01/2014 13:45, Martin Sustrik a écrit :
On 10/01/14 13:14, Laurent Alebarde wrote:Martin Sustrik <sustrik@...> writes: Awsome ! It would be interresting to add in the API some plumbing functions to manipulate the channel ID stack. It would authorize one route for the request, and another one for the response.That would break the req/rep model, no? The vary nature of the pattern is that the reply is delivered to the original requester. Or, if you meant that the reply can use different route to get to the original requester,
Yes
It would permit higher level security protocol tests, like "man in the middle", in an easy way.that's what IP is for... routing around the failure and so on. Why duplicate the functionality on higher level?
Like here: http://tim.dysinger.net/posts/2013-09-16-getting-started-with-nanomsg.htmlBTW, do you have a complete example code somewhere available with scemas please ?What schemas?
