Dave wrote:
>
> >No, no... the user object should _not_ change. What changes is how that
> >object is created, i.e. where the data that populates the User object
> >comes from, in your case an XML store. You are using XML here just like
> >a database, or LDAP. Don't change the data structure, change the data
> >retrieval.
>
> Are you saying to use the existing TurbineUser and just change the Peer
> classes?
Yup. You don't want the application to care whether the data sotrage
format is XML or database anymore than you care if it is Oracle or
mySQL. You want to get the data (where your peer comes in) and then use
it as any other data. This allows you to mix/match/switch data stores
anytime you want.
>
> I was thinking that you could just create a TurbineXMLUser that implements
> User.
I wouldn't. It isn't the user that is different, it is the format that
the user's information is stored in. You don't have a
TurbineOracleUser... why would you have a TurbineXMLUser?
-Brett
>
> Dave
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
