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

mailbox tubes #3

Open
kr opened this issue Apr 23, 2009 · 5 comments
Open

mailbox tubes #3

kr opened this issue Apr 23, 2009 · 5 comments
Labels
FeatureRequest NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made.

Comments

@kr
Copy link
Member

kr commented Apr 23, 2009

Most tubes exist as long as jobs exist in them or a client is watching or using them. Mailbox tubes exist only while a client is watching. If no clients are watching, the tube and all jobs in it vanish.

A common use for this is to indicate completion of a job by a "reply job" sent to a mailbox tube.

Such tubes can be marked as special by prefixing the name with a special char. I think "~" would work fine as that char.

@kr
Copy link
Member Author

kr commented Jun 7, 2010

This falls outside the main scope of beanstalkd's purpose, but I think it opens up a lot of interesting possibilities.

@andreisavu
Copy link

+1 I like the idea of using beanstalkd as a communication bus for actors.

@nodeGarden
Copy link

basically persistance when empty right? I definitely would love this, or some way to create "base" tubes when starting the server. For instance I need 4 tubes that are always there. If I poll them after they empty, then I get uncaught exception... when I think it should just be "no job" message.

Oddly, I've noticed that ONE of my tubes HAS stayed open after emptying... not sure why that one has, and others haven't.

@kr
Copy link
Member Author

kr commented Sep 16, 2011

nodeGarden: this is somewhat different from what you described.
Feel free to post on the mailing list or send me a message with
your other questions, so we don't get too off-topic here.

@JensRantil
Copy link
Contributor

#244 might be related to this.

@ysmolski ysmolski added NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. and removed needs-label labels Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FeatureRequest NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made.
Projects
None yet
Development

No branches or pull requests

5 participants