-
Notifications
You must be signed in to change notification settings - Fork 129
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
stable release #325
Comments
Yes I think the rough plan of @sagikazarmark was to have a stable release by the end of the year. The biggest task will be splitting the drivers out of this repo and into separate packages. About the message status can you explain a bit more what you are trying to do? |
Ok, sometimes we need to tell client whether to wait or try again. So we have to track a job status(waiting, completed or failed) |
I don't think you need to do that. Reference monolog, it have so many drivers. |
I don't know which queue driver you use, but for example the flatfile driver. All messages in the directory are waiting, but when they have the .proceed suffix they are currently being processed and when the file is not in the directory the job is completed (failed jobs are still in the directory, just like a new job) About the driver separation process, this is indeed something that is not necessary. But all the drivers create "soft dependencies" (composer suggests). By moving the drivers to separate packages when are able to declare "hard" dependencies on the required libs. See #256 for the full discussion on this topic. |
Hi there, i have some questions.
The text was updated successfully, but these errors were encountered: