Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modularizing sockets definition. #87

Open
sydcanem opened this issue Jan 8, 2015 · 4 comments
Open

Modularizing sockets definition. #87

sydcanem opened this issue Jan 8, 2015 · 4 comments

Comments

@sydcanem
Copy link
Contributor

sydcanem commented Jan 8, 2015

Hi. Happy New Year!
I'm creating an amqp top layer library and I would like to use your sockets definition. Basically, what I'm planning to do is to manage the amqp connection with reconnection feature when error, basic topology and rpc mechanism with TTL for callbacks. It would be great if I could just pull any of your sockets directly and just supply the required arguments and build the API on top of it. Would this be possible?

Thanks for the library. Cheers!

@squaremo
Copy link
Owner

I'm not quite sure what you're asking for -- can you sketch out how it would look? (In code, or pseudo-code, perhaps)

@sydcanem
Copy link
Contributor Author

It would be great if I could just do:

var ReqSocket = require('rabbit.js').ReqSocket;
// Manage the connection and channel
...
var requester = new ReqSocket(channel, options);

@squaremo
Copy link
Owner

Ah, I see! OK, that is a worthy aim. Let me take a look at it ..

@sydcanem
Copy link
Contributor Author

Looks like this PR #88 seems to work ok. I can now do:

var ReqSocket = require('rabbit.js').REQ;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants