This is another PR for reactphp/stomp#24. It forwards the end event through the InputStream class and through the Client, similar to how errors are handled.

I need to handle server-side restarts, and I can't detect a disconnection without this fix.

Thank you!

Jason

Currenlty this MR does the following

• [x] Switch to PSR-4
• [x] Update the tested PHP versions
• [x] Make sure tests succeed
• [x] Add a docker container to test the things Travis would normally do (it's not completly the same tho :()
• [x] Make sure it works against a recent version of React
• [x] Add tests for ActiveMQ
• [x] squashed commits

Currently ActiveMQ tests are run without auth tests because Ubuntu ActiveMQ 5.6 for some reason doesn't allow plugins

This is a fix for #24

I think we should move the stream_socket_client call when React\Stomp\Client::connect is called. We could provide automatic reconnection that way.

ActiveMQ frames might start with a new-line caracter, producing an offset error in the parser.

Example of ActiveMQ frame :

\nMESSAGE\ncontent-type:text/plain\ndestination:/topic/foo\ntimestamp:1356608654862\ncontent-length:10\npriority:4\n\nle message

Specifically in line 36 of \React\Stomp\Protocol\Parser.php

<?php
/*** snip ***/
public function parseFrameData($data)
{
        $frame = new Frame();

        list($head, $body) = explode("\n\n", $data, 2);

I don't know the protocol well enough to implement a proper fix for compensating when $data is empty.

In the following code, the exit('error'); is never triggered

The bug occurs whenever a process is listening to the port or not.

$loop = React\EventLoop\Factory::create();
$factory = new React\Stomp\Factory($loop);
$client = $factory->createClient(array('port' =>80));

$client
    ->connect()
    ->then(
         function () {},
         function () { exit("error"); }
    );

$loop->run();

• Bump react deps to 1.1.* (@phiamo)
• combined the in 0.6.0 existing ReadableStream and WritableStream into the now also final InputStream and OutputStream classes
• adapted the cancelTimer API change in Client

All Unit tests are green!

I had a dependency clash for react/socket ^1.1.

That version has all classes set as final, so I had to put a bit of effort to learn react/socket and get this package working with it. Hopefully, you're happy with the upgrade. Otherwise, I am open to feedback to get this merged.

Notes:

• I don't think this is a breaking change. I didn't need to update the functional tests.
• I added a connection-status event. It was useful information for me to print in my logs.

This adds the ability to connect to TLS-protected queue brokers, via the 'protocol' option. Update affected unit tests, add functional test (verified against activemq v5.15.0). Also document how to run the functional tests

I'm curious about something. While looking at the network of this repository I've come across the branch of @capablue. They implemented the heartbeat functionality I was looking for and they apparently think it is stable enough because they've added a tag. After some testing locally this does suit our needs.

What I find most interesting is that I can't find any pull request or issues created by Capablue in this repository. Unfortunately the organisation doesn't have any public members so I'm unable to search more in depth and contact people. Is this something worth looking into? Perhaps even forking that repository and create a pull request myself?

I would like to continue to use the official stomp repository instead of a fork. Any thoughts, @igorw?

Link to repository: https://github.com/capablue/stomp