Re: [sensor-dev] Sensor console idea

[Richard S. <rj...@gm...>]

I didn't include Confluence to the list because it not for free, so it will
be difficult to package it with a sensor distro.

The wiki will indeed need to use remoting to Sensor runtime or a Sensor Dat=
a
Store. I prefer an http based protocol to avoid infrastructural issues (lik=
e
firewalls) as much as possble.


On 3/11/06, Age Mooy <age...@gm...> wrote:
>
> or confluence I guess.. that has a good plugin infrastructure.
>
> The problematic part is thinking up good ways of connecting to a
> Sensor runtime. The three scenarios curently supported are:
>
> - through a shared spring context (same VM)
> - through a static wrapper (same VM)
> - through Spring remoting (xfire, hessian, burlap, etc.)
>
> The wiki would almost by default have to use one of the remoting
> protocols. Or am I missing something ?
>
> Age
>
> On 3/11/06, Richard Swart <rj...@gm...> wrote:
> > not really. We need something lightweight with a good plugin structure.
> >
> >  jspwiki for example supports also forms which is something we will
> probably
> > need for selections etc.
> >  Other alternatives might be xwiki, snipsnap.
> >
> >
> >
> >
> >
> > On 3/11/06, Age Mooy <age...@gm...> wrote:
> > > Interesting idea. Something like fitnesse.... which works great for
> > testing.
> > >
> > > Did you have any particular wiki in mind ?
> > >
> > > Age
> > >
> > > On 3/11/06, Richard Swart <rj...@gm... > wrote:
> > > > Just a brainwave, but perhaps it would be a nice idea to use a wiki
> as
> > basis
> > > > for the Sensor Console.
> > > >
> > > >  If could provide some plugins to to:
> > > >
> > > >  - display sensor data as a table\tree
> > > >  - display sensor data as a graph
> > > >  etc.
> > > >
> > > >  This way users are very flexible in creating their own console,
> look &
> > > > feel, add documentation to it, etc. In the future we could even add
> > other
> > > > types of monitoring data to it just by adding plugins.
> > > >
> > >
> >
> >
>