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

Support Services #7

Open
baalexander opened this issue Dec 3, 2011 · 2 comments
Open

Support Services #7

baalexander opened this issue Dec 3, 2011 · 2 comments

Comments

@baalexander
Copy link
Owner

This is a big issue and will likely require smaller, more specific issues going forward.

There's two ways to communicate between nodes in ROS: The publisher/subscriber way passing messages for topics and the RPC way, using service request and service responses. Currently, there is no support for services.

The implementation from a request/response perspective should resemble other RCP implementations, something along the lines of service.request('add_two_numbers', [array, of, parameters], callback) where the callback returns the service response.

tcpros.js will need to be updated and refactored for service supports. But tcpros.js really needs to be refactored anyways. Core service related models should be added to ros.js as well. Most documentation only references publishers and subscribers, so service copy will need to be added too.

@baalexander
Copy link
Owner Author

Look at dnode and now.js.

@baalexander
Copy link
Owner Author

More work needs to go into defining the services usage, but service should resemble the topic API some. The new ros.js has some example code using services, but it's not complete yet either.

Srv files also need to be parsed, similar to msg files.

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

1 participant