No namespace and a strange "type" for Requester and Responder instances about cote HOT 7 OPEN

For some reason I hadn't seen this issue! Sorry.

Namespaces are mainly intended for the Sockend component, and directly map to socket.io namespaces. However, if you look at the Component.js line 29 you will notice that all components make use of namespaces in discovery and connection.

The main reason for why the requester / responder syntax is not like randomRequest.send('topic', json, function(res) { is because the goal was to keep the request object very simple — build a single object however you like, so you don't have to use multiple parameters. On the other hand, sending blobs is something we need to figure out. That was on our list.

Also, yes, I love this discussion and would love to think of a cote v2.

You can also check out kotelett, my attempt to simplify this, plus make connections dynamic, with even less configuration, based on what messages a service could respond to. I intended kotelett to be the next generation of cote.

from cote.

Ok for the namespace, you're right, it's used on discovery.

For the topic subject, that's purely some API/syntax question because I was surprised of the 'type' field. What append if the 'type' is not filled ? Not tested on my side but probably it's not working ?

Joel

from cote.

If there's no type in a request object, the responder throws it away, as it's not a legitimate request.

from cote.

Please check out kotelett. Your suggestion could be easily implemented there, and it's in fact much simpler to use than cote.

from cote.

Well it's not a problem for me, just surprising. On publisher you have:

randomPublisher.publish('update3', { val: 'should not be getting this' });

You have not:

randomPublisher.publish({ type: 'update3', val: 'should not be getting this' });

That's why I said it's only an API/syntax convenience/uniformity across cote library but for my own usage it does not matter.

from cote.

Well it's not a problem for me, just surprising. On publisher you have:

randomPublisher.publish('update3', { val: 'should not be getting this' });

@joelguittet This threw me off when I first started using cote as well. First time I tried using publisher i couldn't get it to work until i realized it takes type as a function argument instead of a key on the payload object.

from cote.

@otothea yeah exactly, publisher is one way and requester is another way. Troubling.

from cote.