The elasticsearch PHP client is an excellent example of a well-written PHP service client. Very simple API with little surface area to memorize, uses PSR logging interface, easily configurable due to pimple-based design.

@igorwhiletrue thanks! I was aware of stackphp/run, but wondered if there was an alternative which left the run method in place — Silex is such an exquisitely designed and concise abstraction it’s a pity to have to give that up and introduce extra packages, namespaces and functions (more surface area to learn and remember).

↪
Sandeep Shetty:
@BarnabyWalters Any chance you might share the "~210 lines of code" with me? If not publicly, maybe a private gist?

@sandeepshetty sure! gist.github.com/barnabywalters/7863676 — included the basic functions plus the convenience class I use and a little demo. Very specific to chronological post storage/indexing, and very much in flux. I’d be interested to hear your thoughts about it.

Had many basic software development lessons hammered in by personal experience over the last couple of years: hierarchy bad. side effects bad. many moving parts bad. undue complexity bad. inconsistency bad. SQL databases fragile. always be reducing.

I just faked having a task queue for #taproot#indieweb note posting tasks using Symfony HttpKernel::terminate() and it was the easiest thing ever.

Instances or subclasses of HttpKernel have a terminate($request, $response) method which, if called in the front controller after $response->send(); triggers a kernel.terminate event on the app’s event dispatcher. Listeners attached to this event carry out their work after the content has been sent to the client, making it the perfect place to put time-consuming things like POSSE and webmention sending.

Once you’ve created your new content and it’s ready to be sent to the client, create a new closure which carries out all the the time consuming stuff and attach it as a listener to your event dispatcher, like this:

Then, provided you’re calling $kernel->terminate($req, $res); in index.php, your callback will get executed after the response has been sent to the client.

If you’re not using HttpKernel and HttpFoundation, the exact same behaviour can of course be carried out in pure PHP — just let the client know you’ve finished sending content and execute code after that. Check out these resources to learn more about how to do this:

Further ideas: if the time consuming tasks alter the content which will be shown in any way, set a header or something to let the client side know that async stuff is happening. It could then re-fetch the content after a few seconds and update it.

Sure, this isn’t as elegant as a message queue. But as I showed, it’s super easy and portable, requiring the addition of three or four lines of code.