RE: ObjectRepository update

Hi Shawn,

> While making these changes a question came to mind. What does the
> StateMap interface offer that the java.util.Map interface doesn't? It
> looks like it simply uses an alternate naming convention but only
> includes a handful of the functions. Anyone have a better idea?

That's exactly what it offers. The reason for using different naming was so
that you could have a map which actually implements "state" as well as
containing data.

Basically, what drove the development of this originally was the need to
define objects that carried data - whether Maps, Lists, Context structures,
etc, that could also have "state" information associated with them. So I
tried to come up with something as simple as possible that used a
nomenclature (putState, getState) that wouldn't conflict with other
interfaces.

That help?

Christian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"


> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Shawn Wilson
> Sent: Friday, September 26, 2003 11:35 AM
> To: [email protected]
> Subject: [Barracuda] ObjectRepository update
>
>
> I just checked in an update to ObjectRepository that fixes a bug but
> also changes the way most of the classes within that file are coded to
> prevent a similar bug in the future. I'm pretty sure it all still works
> now but just in case now you know how broke it :).
>
> Here's the comments from my commit:
>
> --- Begin comments ---
> saw_092603_1 - Recoded most of the classes within ObjectRepository to
> fix a current bug but more importantly to prevent the same type of bug
> in the future. Specifically the clearState() method was not being
> overridden. The way the classes were coded, they extended from
> ObjectRepository (and therefore DefaultStateMap) but in fact was not
> utilizing anything provided from those classes.
> --- End comments ---
>
> You can find additional comments directly in the file tagged with
> saw_092603_1.
>
> While making these changes a question came to mind. What does the
> StateMap interface offer that the java.util.Map interface doesn't? It
> looks like it simply uses an alternate naming convention but only
> includes a handful of the functions. Anyone have a better idea?
>
> Thanks,
> -shawn
>
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda