crossbario / crossbario/autobahn-python
Process-to-WAMP example
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
I've been asked whether we could add an example how to communicate with a forked process via WAMP - eg expose the functionality of an executable that is then started dynamically.
There are 2 scenarios here:
- the executable should be started, left running and communicated with over pipes. A WAMP session then exposes eg a procedure, and when that is called, some communication over (the existing) pipes happens
- the executable should be started "one shot", that is, upon an incoming call to a WAMP registered procedure, the executable should be forked (presumably with command line args and/or stdin derived from the WAMP call parameters) and waited for exit.
This could reside as a new example here: https://github.com/crossbario/autobahn-python/blob/master/examples/twisted/wamp/app/process2wamp
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing examples/twisted/wamp/app/process2wamp location and the surrounding Twisted WAMP examples. Define how the example should demonstrate both a persistent fork communicating over pipes and a one-shot executable invoked from a registered procedure; done means the example clearly covers the requested process-to-WAMP interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100