We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The peek commands let the client inspect a job in the system. There are four variations. All but the first operate only on the currently used tube.
"peek \r\n" - return job .
"peek-ready\r\n" - return the next ready job.
"peek-delayed\r\n" - return the delayed job with the shortest delay left.
"peek-buried\r\n" - return the next job in the list of buried jobs.
There are two possible responses, either a single line:
Or a line followed by a chunk of data, if the command was successful:
FOUND <id> <bytes>\r\n <data>\r\n
is the job id.
is an integer indicating the size of the job body, not including the trailing "\r\n".
is the job body -- a sequence of bytes of length from the previous line.
The text was updated successfully, but these errors were encountered:
vimukthi-git
No branches or pull requests
The peek commands let the client inspect a job in the system. There are four
variations. All but the first operate only on the currently used tube.
"peek \r\n" - return job .
"peek-ready\r\n" - return the next ready job.
"peek-delayed\r\n" - return the delayed job with the shortest delay left.
"peek-buried\r\n" - return the next job in the list of buried jobs.
There are two possible responses, either a single line:
the requested state.
Or a line followed by a chunk of data, if the command was successful:
is the job id.
is an integer indicating the size of the job body, not including
the trailing "\r\n".
is the job body -- a sequence of bytes of length from the
previous line.
The text was updated successfully, but these errors were encountered: