This repository has been archived by the owner on Nov 17, 2021. It is now read-only.
Alternative file spool implementation. #187
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flexability then the standard Swift_FileSpool class.
makasim
pushed a commit
to formapro-forks/swiftmailer
that referenced
this pull request
Jul 26, 2017
…ssue swiftmailer#187; the priority levels can be adjusted either through the handler's constructor or setters
|
I'm closing this PR as the Swiftmailer spool system does not work well and will soon be much better when we will replace Swiftmailer by Symfony Mailer. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Provides a new Swift_SerializedFileSpool class as an alternative to the standard Swift_FileSpool class.
Main benefits is that it can use the igbinary_serialize and gzcompress functions if available to further reduce the size of spool files. It also provides a bit more control over the generated spool files.
Most of the changes could have been incorporated into the existing spool class but there are are a few slight differences in implementation. Having a new class with slightly different naming conventions can also ensure that even if the two spool classes use he same directory they won't walk over each other.