Re: Streamlined application/script development [Re: coding an Application in perl]

Chapman Flack <[email protected]> Wed, 1 Nov 2017 23:37:23 -0400
Newsgroups gmane.comp.archivers.amanda.devel
Message-ID <[email protected]>
On 10/23/17 17:52, Chapman Flack wrote:
> On 09/13/2017 01:10 PM, Jean-Louis Martineau wrote:
> 
>> Amanda already require the perl JSON module, so you can use it.
> 
> I notice you are adding some recent code that may use DBD::SQLite
> for catalogs. Is that becoming ok to depend on now? On a server
> only, or server and client?

This question is more or less on my critical path now, because of the
various review comments on the pull request, state management for
scripts (exploiting the new server session timestamp) is about the only
one remaining for me to work on.

Local state for applications was relatively simple (each one just
keeps its own file per DLE), but if scripts are to be able to cache
state per session-timestamp (and somehow efficiently see and manage
expired cached states), and possibly set properties for later-running
scripts in the session, a shared file with better concurrency-control
properties might be desirable. That would come essentially for free
with SQLite, if it is already expected to become a dependency anyway.

-Chap