Conversation:
Notices
-
@takeshitakenji When its complete I'd love to have a queue handler in postActiv which is actually modern.
-
@takeshitakenji It shouldn't be too hard, since it's basically just an interface to the queue entries in the DB. Ideally, we should be railroading around that anyways for performance reasons.
-
@takeshitakenji What you want to do, I would think, is claim EVERYTHING you can in the database, and stick it in redis, and only page it back to the DB when all else fails. I doubt we'll have much use for that error case, but we should still have it in the design that if for some reason the new queue handler fails we fall back to the daemons/OQM/whatever
-
@takeshitakenji Remember that you can overload methods if you want, and change their behaviour. It won't break anything in and of itself as long as the inputs and outputs are still what GS/postActiv "expects"
-
@takeshitakenji The only one you can run into problems overriding is QueueManager::get() - you need to make sure you have the other queue types in there in case your queue is installed but the user has specified in config.php to use another queue.
-
@takeshitakenji You could model it off a child class that does most of what you need already, definitely!
-
@takeshitakenji This sounds like it should work!
maiyannah
All Hacker Poesy content and data are available under the