[cas-dev] BerkeleyDB ticket registry

[March, Andres]

Actually, my implementation is not distributed, just persisted.
Berkeley DB supports clustering but only in a single master
configuration.  This limitation means you could only have one node
creating tickets.  This could still be useful but would require a more
complex architecture, like:

            master                                      master

             /    |     \
/    |    \

           /      |       \                                     /      |
\

     slave  slave  slave                        slave  slave  slave

 

Google Accounts uses this type of architecture.

 

The registry I created just makes it easier to store long-lived tickets
without worrying about memory or server restarts.  I have applied for
approval from my manager to contribute this code.

 

________________________________

From: cas-dev-bounces at tp.its.yale.edu
[mailto:cas-dev-bounces at tp.its.yale.edu] On Behalf Of Scott Battaglia
Sent: Wednesday, January 03, 2007 8:23 PM
To: Mailing list for CAS developers
Subject: Re: [cas-dev] BerkeleyDB ticket registry

 

In the HEAD for the 3.1 release I've also created an
AbstractDistributedTicketRegistry class.  I am not sure if that could be
useful for this implementation.

Thanks
-Scott

On 1/3/07, Scott Battaglia <scott.battaglia at gmail.com> wrote:

This could be a great addition to give people multiple options for
distributed registries.  If you get management approval, please create a
JIRA issue.

Thanks!
-Scott

 

On 1/3/07, March, Andres <amarch at soe.sony.com> wrote:

I will seek approval from my manager and add a JIRA issue with a patch.

> -----Original Message-----
> From: cas-dev-bounces at tp.its.yale.edu [mailto: cas-dev-
<mailto:cas-dev-> 
> bounces at tp.its.yale.edu] On Behalf Of Andrew Petro
> Sent: Wednesday, January 03, 2007 3:59 PM 
> To: 'Mailing list for CAS developers'
> Subject: Re: [cas-dev] BerkeleyDB ticket registry
>
> Yes.
>
> ________________________________________
> From: cas-dev-bounces at tp.its.yale.edu 
> [mailto:cas-dev-bounces at tp.its.yale.edu] On Behalf Of March, Andres
> Sent: Wednesday, January 03, 2007 3:21 PM 
> To: Mailing list for CAS developers 
> Subject: [cas-dev] BerkeleyDB ticket registry
>
> I have made a simple BerkeleyDB ticket registry. Anybody interested?
>
>
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev

_______________________________________________
cas-dev mailing list
cas-dev at tp.its.yale.edu
http://tp.its.yale.edu/mailman/listinfo/cas-dev 





 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20070104/28d254be/attachment.html