Kedar,
To determine how to proceed with AMX, I need to be clear on the
behavior--
1. Can the "old" attributes still be set (changed)?
2. Are the "old" attributes used at all?
3. Does it make sense to have AMX "patch through" the old names to
the new ones?
Thanks,
Lloyd
----------------
Solution: Since we can't "remove" the attributes because that means
old XML can't validate against new DTD, we are deprecating these
attributes and introducing correctly named attributes as optional ones.
We have done a similar thing with security-service element. There is
no change in the semantics of the attributes, AFAIK.
What is changing: The element http-protocol will be:
<!ATTLIST http-protocol
version CDATA "HTTP/1.1"
dns-lookup-enabled %boolean; "false"
forced-type CDATA "text/html; charset=iso-8859-1"
default-type CDATA "text/html; charset=iso-8859-1"
forced-response-type CDATA "AttributeIsDeprecated"
default-response-type CDATA "AttributeIsDeprecated"
ssl-enabled %boolean; "true">
instead of:
<!ATTLIST http-protocol
version CDATA "HTTP/1.1"
dns-lookup-enabled %boolean; "false"
forced-response-type CDATA "text/html; charset=iso-8859-1"
default-response-type CDATA "text/html; charset=iso-8859-1"
ssl-enabled %boolean; "true">