----- Original Message -----
From: george stewart <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Monday, December 27, 1999 6:25 PM
Subject: Re: CVS update:
turbine/src/java/org/apache/turbine/opl/apiAttr.java
>
>
> --- jon * <[EMAIL PROTECTED]> wrote:
> >Attributes should be order based.
> > The current implementation
> > puts things into a hashtable and that is bad since
> > the attributes can get
> > out of order. We have run into this issue with ECS
> > and attributes to Html
> > entities. With Html, attributes can be any order.
> > With newer technologies
> > (XML) attributes need to be in a specific order.
> > This will probably bite you
> > later so you might as well fix it now.
> >
> If this is true, isn't this sufficiently encapsulated
> to soften the impact of change. All the access is
> with the Attributed interface. If order is required,
> shouldn't be the end of the world.
>
> P.O. holds an AttribuedImpl. Even P.O. doesn't know
> it has a hashtable. In the early code, I used
> hashtable, but substituted with AttributedImpl.
> The outside world gets an enumeration of attrs.
>
this will have a direct effect on the ObjectSet which the order of
attributes is vital. I think a Vector should be used. Even though
"...outside world gets an enumeration of attrs..." there is no guarantee
that the enumeration will be in the same order as they went in.
that's my $0.02
-scott-
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
