A +1 on durability, but a -1 on assuming it can't be in a high- availability in-memory cache.
Mark.
On 15 Jul 2009, at 01:29, David Lutterkort wrote:
On Tue, 2009-07-14 at 00:44 -0400, Bob McWhirter wrote:
So, is session state too much state? I think it'd be okay to store in RAM, no guarantee on longevity, and requires no local long-term storage.
From an ease-of-use POV, it would be much nicer if libcloud had a
concept of session, and with that enough state to store credentials for each backend.
For a service that exposes the libcloud API though that storage must be persistent, and not just in memory: otherwise users of the API will get very strange errors when the service is restarted in the middle of one of their sessions. Basically, they'd have to expect a 'sorry, forgot your credentials' error on every API call, and then login again and redo the call.
I think though that the storage could be simple files in /var/lib or similar (or a simple sqlite database) by default.
David
Libcloud-list mailing list Libcloud-list@redhat.com https://www.redhat.com/mailman/listinfo/libcloud-list
--- Mark Little mlittle@redhat.com
JBoss, by Red Hat Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt Parsons (USA) and Brendan Lane (Ireland).