I have build an application with Camel using websockets, and bootstrap for
the UI - livephotostream.com
In that application all the static files are actually on different server
(amazon s3) and they interact with the camel application (on EC2) using
websockets.
Using an in memory component to
Another alternative would be to have the camel routes publish the data to
some in memory data structure.
Then your display/monitor system could read from this. The advantage here
is that your monitoring system will survive refreshes.
On 20 October 2012 09:43, Claus Ibsen claus.ib...@gmail.com
On Wed, Oct 10, 2012 at 8:55 PM, gonzalo diethelm gdieth...@dcv.cl wrote:
I'm back on this list after some time; apologies if this is obvious or
previously discussed.
I am thinking of the following architecture for a monitoring system:
1. A set of Camel routes that gather the
I will try to bump this question just once. Any hints from anybody?
--
Gonzalo Diethelm
DCV Chile
-Original Message-
From: gonzalo diethelm [mailto:gdieth...@dcv.cl]
Sent: Wednesday, October 10, 2012 3:56 PM
To: users@camel.apache.org
Subject: Camel, websockets and Javascript
