Re: Long Life Objects
- From: timeisfire8@xxxxxxxxxxx
- Date: 31 Mar 2007 13:00:06 -0700
Thanks fo the post Mark Nicholls. Fowler's enterprise patterns are
mentioned often and I will take a look at them.
Lahman
So before I can speculate on an answer you are going to have to put some
more words around what you want to do with defaults.
Let me give the GUI scenario for an Admin user:
1) User loads the application for the first time and no address types
are predefined.
2) User must create whatever address types are desired with no
restriction on quantity or naming.
3) User decides to create two address types named 'Delivery 1' and
'Delivery 2'. Please note that no actual addresses have been created
yet, the user is just defining types.
4) When creating the 'Delivery 1', user selects a checkbox 'Use this
as the default delivery address type for all customers'.
Following this sequence, any 'Delivery 1' addresses that are created
in the future will be used as the default for all areas of the app
that require the selection of a delivery address, on the basis that it
will be the correct one 90% of the time. This is the purpose of the
'isDefault' attribute of AddressType as it currently stands. I would
be perfectly happy to scrap [AddressType] but would then need a way to
remember that every Delivery 1 Address that was created in the future
should have a true attribute 'isDefault'.
Hope that explains it clearly.
.
- References:
- Long Life Objects
- From: timeisfire8
- Re: Long Life Objects
- From: H. S. Lahman
- Re: Long Life Objects
- From: timeisfire8
- Re: Long Life Objects
- From: H. S. Lahman
- Re: Long Life Objects
- From: timeisfire8
- Re: Long Life Objects
- From: H. S. Lahman
- Re: Long Life Objects
- From: timeisfire8
- Re: Long Life Objects
- From: H. S. Lahman
- Long Life Objects
- Prev by Date: Re: Metaphor-oriented programming
- Previous by thread: Re: Long Life Objects
- Next by thread: Re: Long Life Objects
- Index(es):
Relevant Pages
|