My advice is to work by identifying problems rather than solutions.

Do not make stuff except by improving what there is, step by step,
where you can identify real problems.

For a start here, see how something like Zyre fits your use case and
identify problems with that.


On Fri, Dec 13, 2013 at 3:56 PM, crocket <[email protected]> wrote:
> I didn't think of any term for my technology.
> I think it contains
> 1) a form of RPC interface exchange
> 2) methods grouped in namespaces.
>
> For now, the simplest approach I can think of is a ZeroMQ socket for each
> namespace.
>
>
>
> On Fri, Dec 13, 2013 at 8:15 PM, Arnaud Loonstra <[email protected]> wrote:
>>
>> On 12/13/2013 12:05 AM, crocket wrote:
>> > I'm not good with current module systems because they are difficult to
>> > use and maintain.
>> > Binding modules from other languages is difficult with FFI(Foreign
>> > language interface).
>> >
>> > Publishing namespace or answering namespace requests via zbeacon would
>> > be convenient.
>> > Each namespace has a list of methods or even variables. Namespace
>> > collisions can be detected via UDP discovery.
>> > Module inspection API might answer what serialization protocols they use
>> > and serve method signature requests.
>> >
>> > For now, that's all, and it seems simple and easy enough.
>> >
>> > Since I'll have been tied to a 9-6 job until Feb 2015 by some serious
>> > laws and commute takes 4 hours a day, I may not have time until then. So
>> > it's just an idea for now.
>>
>> Can you elaborate a bit more about what you mean? I'm not sure if I can
>> follow you? It sounds like you are suggesting an RPC interface exchange?
>> In regards to zbeacon/zyre I think the headers should be used to
>> exchange capabilities.
>>
>> Arnaud
>> --
>> w: http://www.sphaero.org
>> t: http://twitter.com/sphaero
>> g: http://github.com/sphaero
>> i: freenode: sphaero_z25
>> _______________________________________________
>> zeromq-dev mailing list
>> [email protected]
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to