Does WAMP server use a message queue broker? - Autobahn

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Does WAMP server use a message queue broker?
Received-SPF: pass (google.com: domain of tobias.oberst...@gmail.com designates 209.85.214.52 as permitted sender) client-ip=209.85.214.52;
Message-ID: <50229F63.9000...@gmail.com>
Date: Wed, 08 Aug 2012 19:18:27 +0200
From: Tobias Oberstein <tobias.oberst...@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: autobahnws@googlegroups.com
CC: PC <paddy.car...@gmail.com>
Subject: Re: Does WAMP server use a message queue broker?
References: <ffacf630-7c78-4b86-a2cc-70dfcea9953a@googlegroups.com> <5020CB34.4030...@gmail.com> <3efcc8a8-fbb5-4dee-81f5-8209136d2ac9@googlegroups.com> <502186EE.4060...@gmail.com> <21edda6a-155a-48ef-be20-8eb52ce31fec@googlegroups.com> <50229350.1000...@gmail.com> <805338d2-d4d4-4c31-9f8d-6d9a7de524dd@googlegroups.com>
In-Reply-To: <805338d2-d4d4-4c31-9f8d-6d9a7de524dd@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Am 08.08.2012 19:06, schrieb PC:
>
>
> On Wednesday, August 8, 2012 9:26:56 AM UTC-7, Tobias Oberstein wrote:
>
>      >     Now you lost me: do you want a) to have logic in your
>     background server
>      >     processes that you can call from WAMP clients via RPC, or b)
>     have
>      >     logic in your background processes that get called when
>     events are
>      >     published by WAMP clients?
>      >
>      > a). similar to what you have defined in WAMP.
>
>     In this case you can use
>
>     registerHandlerMethodForRpc
>     registerHandlerProcedureForRpc
>
>     where you then can implement the communication with your background
>     processes.
>
>     When your background processes boot up, they also need to announce the
>     RPC endpoints they provide via IPC to the WAMP server which then needs
>     to setup the fowarding like above.
>
>     What language(s) are the background programs written in?
>
>     PHP currently. But since they are different processes, they can be
>     written in any language. This is one of the features that I'm
>     shooting for.
>

Ok, I really know too little to give a thorough advice on architecture
on such a thing. Just a couple of further hints:

- Who will be responsible for starting and monitoring the background 
processes (if one fails, who restarts etc)?
- Will those programs always run locally together with the frontend WAMP 
server?
- Essentially, you will need to have something like WAMP (at least the 
RPC part) over IPC
- In a way thats not sufficient, since the frontend WAMP server needs to 
know what RPC endpoint are available .. on which program

For PHP (standalone), there is a WAMP server implementation: Ratchet.

For transparent forwarding of WAMP RPCs to anything that exposes
a REST/HTTP or Ext.Direct API, our commercial offering Tavendo WebMQ
is capable of doing that. You can call from any WAMP client via 
WebSocket into anything with REST or Ext.Direct API today, and
database stored procedures in the coming future. You can also push
PubSub events from within your PHP i.e. This is a feature of WebMQ.
WebMQ is an integration server based on Autobahn, with a whole range
of flexible integration options.

Should a commercial offering be of interest to you, we should talk
and determine if it already could do what you want, and if not if
we can make that feature available.

Cheers,
Tobias
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
