Services are already pluggable. Each service is identified by a runtime string. Instead using “masar/save” you use “foo/save”. No extra work to do. The only way that you can make it not pluggable is if you hardcoded the String in the Java code…

 

Gabriele

 

From: Eric Berryman [mailto:eric.berryman@gmail.com]
Sent: Monday, March 31, 2014 9:27 AM
To: Kasemir, Kay
Cc: CSS-Core
Subject: Re: [Cs-studio-core] save/ restore for CSS - anywhere?

 

 

What would be nice ... Vasu, here at MSU, has been needing these VType->NTTypes to be serialize-able to put in a database (and json representation).  If we could make the plugin save these objects to file or to MASAR, or to database; that would be great?  No?

... but yes on, making the config/persistence pluggable.

 

On Mon, Mar 31, 2014 at 9:08 AM, Kasemir, Kay <kasemirk@ornl.gov> wrote:

Hi:

Would it make sense to combine these?
Start with the PVTable as a UI, making the config/persistence pluggable:
One implementation uses the existing files, another uses the MASAR service?
That way, somebody who downloads a basic CSS can start standalone using files,
and once you setup MASAR you can save/restore to it?

Thanks,
Kay


On Mar 31, 2014, at 8:49 AM, Eric Berryman <eric.berryman@gmail.com> wrote:
> We at FRIB would like to implement the BNL MASAR (save/restore) in CS-Studio.  Because MASAR uses PVAccess, Matej's plugin for pvaccess to PVManager would give a good start (the interface itself just using VTypes).

On Mar 31, 2014, at 8:55 AM, "Kasemir, Kay" <kasemirk@ornl.gov> wrote:
> The PVTable contains several elements for this

> ...

> What it doesn't have:

> ...

> MIght also be good to make the persistence pluggable:
> By default, the channel list and saved values are written to files, but each site can provide a site-specific implementation that writes to an RDB or whatever they prefer.