Very sorry for the late response, can't seem to keep up with time
@Tobias, I couldn't figure out why autobahn wouldn't accept the ws
handshake, built my own (very very primitive) ws client.However I
So you try to run AutobahnJS (WAMP v1 version) against Ratchet 0.3? That is supposed to work.
realized the issue might not be with autobahn at all, but with Chrome,
it seems my server receives an empty header, but Firefox connects just
fine. I've got a bone to pick with chrome...I shall try autobahn once
@Chris, sure, I'd be glad to help, but I do need this project...
Let me throw in my thoughts ..
a) a complete and interoperable WAMP v2 implementation in PHP ..
b) on top of an evented networking framework ..
c) that implements the client roles (Caller/Caller/Publisher/Subscriber)
Regarding c), that means that in
Browser (Caller) ----> XXX (Dealer) ----> PHP* (Callee)
the XXX could be any WAMP v2 router. The library for PHP would provide only *. Technically, this library would need to be a WebSocket _client_ that connects to XXX. Note that this doesn't mean that the PHP app based on the library couldn't act as a "whatever" server at the same time. The big advantage is that user can deploy any WAMP v2 router.
This is also mentioned here:
Regarding b), my PHP insight/experience isn't sufficient. Ratchet is based on React https://github.com/reactphp/react
Regarding a): I hope to find time to extend the Autobahn testsuite for WAMP v2 soon. But I think the specification document of WAMP v2 is already orders more complete and precise than WAMP v1.
Am 08.03.2014 07:28, schrieb Grim Lodaf:
From my perspective, it would be awesome to have
once again, apologies for the late reply.
On Tuesday, March 4, 2014 9:33:53 PM UTC+3, Chris Boden wrote:
Ratchet currently supports WAMP/v1 but will support v2. Grim, if
you're willing to contribute we can work through GitHub issues
around the ticket
On Monday, 3 March 2014 13:42:48 UTC-5, Tobias Oberstein wrote:
Am 03.03.2014 19:36, schrieb Grim Lodaf:
> This is my understanding of how WAMP works: After establishing a
> websocket connection(i.e a successsful handshake),
> the server sends a welcome message.Is this correct?
Autobahn>JS was recently upgraded to WAMP v2 "Basic Profile":
For the spec to WAMP v1, that's linked in above page also.
With WAMP v2, the WAMP handshake starts with the client sending
> For a Autobahn.js, is the websocket protocol handshake any
> than it is while using raw ws?
The WAMP handshake only starts after the WebSocket opening
already finished, and the WAMP handshake is already using WebSocket
> If so, how? And where can I get this sort of information?
> I am writing a WAMP server(php), and I can't get autobahn to
> connection.It works on raw ws though(without the
> Websocket-Server-Protocol header).
Ratchet, the only WAMP server I am aware of, currently is at
So a WAMP v2 server would certainly be welcome!
An alternative might be to coordinate with Ratchet and consolidate
efforts there .. Chris?
> You received this message because you are subscribed to the
> Groups "WAMP" group.
> To unsubscribe from this group and stop receiving emails from
> an email to wampws...@googlegroups.com.
> For more options, visit
You received this message because you are subscribed to the Google
Groups "WAMP" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to wampws+un...@googlegroups.com
For more options, visit https://groups.google.com/d/optout.