On Fri, Mar 28, 2014 at 4:20 AM, Fraser Adams wrote:
> I mentioned the other day about the lack of API documentation for things
> like message and codec/data
>
Yeah, I missed those in my documentation pass a few weeks ago.
>
> It'd be really useful to have documentation for at least the non-ob
On 03/28/2014 01:36 PM, Chris Richardson wrote:
Ah, now we are really opening Pandora's box! ;)
The term "client" here is actually quite a simplified term and actually
refers loosely speaking to a system managing a number of products on
that... client. Both the management system and the products
Thanks v. much for the quick response Rafael.
Cheers,
Frase
On 28/03/14 14:38, Rafael Schloming wrote:
On Fri, Mar 28, 2014 at 4:20 AM, Fraser Adams
wrote:
I mentioned the other day about the lack of API documentation for things
like message and codec/data
Yeah, I missed those in my document
Ah, now we are really opening Pandora's box! ;)
The term "client" here is actually quite a simplified term and actually
refers loosely speaking to a system managing a number of products on
that... client. Both the management system and the products should be
individually identifiable and addressab
On 03/28/2014 11:22 AM, Chris Richardson wrote:
Static routes might be ok for a prototype, but a production system would
have many hundreds or even thousands of clients frequently being added and
removed. My assumption is that a static configuration would incur a much
higher management overhead?
On 03/28/2014 12:53 PM, Gordon Sim wrote:
On 03/28/2014 11:22 AM, Chris Richardson wrote:
Static routes might be ok for a prototype, but a production system would
have many hundreds or even thousands of clients frequently being added
and
removed. My assumption is that a static configuration woul
Static routes might be ok for a prototype, but a production system would
have many hundreds or even thousands of clients frequently being added and
removed. My assumption is that a static configuration would incur a much
higher management overhead?
2014-03-28 10:51 GMT+00:00 Gordon Sim :
> On 03
On 03/27/2014 03:33 PM, Chris Richardson wrote:
Hi mailinglist,
I'm trying to set up a broker federation topology with a server and (for
prototyping) two clients and I need to send messages from one client to the
other, routed via the server broker since the clients will be
firewalled/NATed and
I mentioned the other day about the lack of API documentation for things
like message and codec/data
It'd be really useful to have documentation for at least the non-obvious
calls.
One thing I'm currently struggling with is understanding the
ownership/responsibility for the memory of items t
