Server sent events in PHP

Server sent events are really pretty cool. They let your application function a little bit more like an application and a little less than a click adventure in the web wonderland. They are very simple to code and allow your backend code to notify your frontend of progress or other changes.

I could get into trouble for this class comment

At time of writing they are not supported by Internet Explorer ( see here ) but hopefully Microsoft will either stop making Internet Explorer or bring it up to speed with modern browsers. Yeah I know that's not going to happen, but we can wish right?

You don't need to retain an open connection for every visitor to your site because browsers will reopen a closed connection after a few seconds. The additional load for implementing SSE seems to be manageable according to people like this guy who have done tests.

My first project implementing them was for a database consistency tool that is intended to be run against the database in off-peak times to verify that things are as we expect them to be. Basically I wanted a tool to check for dirty data, but more importantly to audit the financial transactions occurring on our site. I wanted to play with SSE so implemented them as a notification service. As the program runs through the various batches of tests it spits out information to the frontend about what it's busy with, if it found an error, and other interesting snippets.

There are bunches of tutorials available on them out there so I'm not going to paste code.

One thing that did concern me a bit is the possibility of forged messages. It's pretty simple to check the origin of incoming messages against a whitelist of domains. Here is an example from html5rocks.com that has a simple origin validation:

 source.addEventListener('message', function(e) {  
  if (e.origin != 'http://example.com') {  
   alert('Origin was not http://example.com');  
   return;  
  }  
  ...  
 }, false);

Personally I think SSE should be in the toolkit of any web application developer.

Comments

Solving Doctrine - A new entity was found through the relationship

There are so many different problems that people have with the Doctrine error message: exception 'Doctrine\ORM\ORMInvalidArgumentException' with message 'A new entity was found through the relationship 'App\Lib\Domain\Datalayer\UnicodeLookups#lookupStatus' that was not configured to cascade persist operations for entity: Searching through the various online sources was a bit of a nightmare. The best documentation I found was at http://www.krueckeberg.org/ where there were a number of clearly explained examples of various associations. More useful information about association ownership was in the Doctrine manual , but I found a more succinct explanation in the answer to this question on StackOverflow . Now I understood better about associations and ownership and was able to identify exactly what sort I was using and the syntax that was required. I was implementing a uni-directional many to one relationship, which is supposedly one of the most simpl...

Grokking PHP monolog context into Elastic

An indexed and searchable centralized log is one of those tools that once you've had it you'll wonder how you managed without it. I've experienced a couple of advantages to using a central log - debugging, monitoring performance, and catching unknown problems. Debugging Debugging becomes easier because instead of poking around grepping text logs on servers you're able to use a GUI to contrast and compare values between different time ranges. A ticket will often include sparse information about the problem and observed error, but if you know more or less when a problem occurred then you can check the logs of all your systems at that time. Problem behaviour in your application can occur as a result of the services you depend on. A database fault will produce errors in your application, for example. If you log your database errors and your application errors in the same central platform then it's much more convenient to compare behaviour between...

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred. The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change. Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal. One way to decouple your domain logic from both persistence and controller is to use the "repository pattern". Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...

Adventures in IT

Search This Blog