From: snacktime <snacktime@...>
Date: 2005-09-20T16:16:15+09:00
Subject: Suggestions wanted - customized ruby http server

------=_Part_7710_25519142.1127200572659
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I'm looking at the options available in ruby to replace an ajax driven=20
client/server application in perl. The application is an interface to the=
=20
asterisk manager api. You can see=20
http://www.voip-info.org/tiki-index.php?page=3DAsterisk+Manager+API for mor=
e=20
information on the api.

The perl application runs a small webserver and monitors asterisk for=20
events, sticking new events into a queue for clients to retrieve. The clien=
t=20
uses ajax to poll the server every few seconds, get any waiting event=20
messages, and possibly send commands to be passed on to asterisk. Right now=
=20
the perl app is written in POE, a perl event driven framework.

The httpd component needs to be able to service multiple simultaneous=20
requests (although not a lot). The asterisk component will only need to ope=
n=20
a single long lasting connection to a single asterisk server. Both=20
components will need some type of message queue to pass messages back and=
=20
forth.

My first thought is to just use rails for the web component, a custom tcp=
=20
client/server for the asterisk component, and drb for the communication=20
between the two. For the message queue I could probably just use arrays to=
=20
build simple FIFO lists for incoming and outgoing messages.

Any thoughts?

------=_Part_7710_25519142.1127200572659--