Hi all,
At the moment, there doesn't appear to be a way to easily and globally
identify a beanstalk job. I've got a use case where I'd like to log a
beanstalk job's id and use it to tie the producer and consumer
together after the fact that would be easier if this were the case. It
seems like the logical way to do this is for the server to compute a
GUID at startup (I'm thinking {fixed size uname() prefix or hash}#
{padded timestamp}#{random number} where # is concatenation?). Then
{server GUID}#{job ID} is globally unique and clients can cache their
server GUIDs for performance. It seems like the easiest thing to do
would be to add this to stats, but it might also make sense to make it
a new command. What are your all's thoughts on the proposal?
I'm happy to modify the code and submit it, but figured I'd see if the
design seemed reasonable to you all before I did.
-Fred
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"beanstalk-talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
