Re: [sensor-dev] Code checked in

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

Hi Age, Jurjan,

The tree concept looks interesting and powerful (as far as I understand 
it). I suppose you want to expose this through the admin  interface (so 
we will need a tree viewer?) . In a way this makes everything a little 
bit more complicated (or advanced) a I anticipated.

I played a little bit with the plugin idea. Probably the easiest way to 
do this is to use Spring. The idea is as follows:

- We'll have scheduled jobs per sensor type. One for Timers, one for 
Counters, one for Gauges.
- Each job will take (through dependency injection) a list of beans that 
implements either a TimerDataExportService,  CounterDataExportService, 
......
- The job will iterate through the list of injected beans and will call 
getDataAndReset() and persist the data.

This way we can plug any component implementing one (or all) Export 
interfaces just by adding them to the spring config (probably a separate 
one just for this) . Would this be flexible enough? Any drawbacks?

As a next step I propose we focus on defining the import, export and 
admin interface. After this Age could continue to concentrate on the 
core stuff (assuming he likes that) and Jurjan and I can work on some 
other items.

Richard

Age Mooy wrote:

>Yo,
>
>I didn't have much time this weekend but I managed to checkin my
>experimental core code. The CVS structure as of now looks like this:
>
><cvsroot>/sensor/sensor-core
>
>So just checkout the "sensor" module and you're set. The sensor-core
>project is an eclipse project with a generated (by mevenide) and
>edited maven project file. I tried the maven build and it works fine,
>which is pretty easy since there are no build dependencies yet :)
>
>What is there:
>
>- The basis for the internal storage stuff in the "internal" package
>- Some empty interfaces for the public API
>
>The code is full of todos and source code comments so just check it
>out and tell me what you think.
>
>Age
>
>PS
>The sourceforge CVS stuff is pretty well documented. You'll have to go
>through the public key exchange process before you can checkout the
>code as a developer instead of anonymously. All current (known)
>readers of this list are developers on the project and should have
>write access.
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
>_______________________________________________
>Sensor-developer mailing list
>Sen...@li...
>https://lists.sourceforge.net/lists/listinfo/sensor-developer
>
>  
>