axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <>
Subject Re: Removal of prefix from HeaderBlock
Date Thu, 22 Jul 2004 04:18:19 GMT
"Susantha Kumara" <> writes:
> IMO if a server is expecting a specific prefix it is wrong. It is the
> namespace that is represented by a prefix is important. Please correct
> me if I am wrong.


There may be crappy servers that only work with certain prefixes ..
that server is broken but if you have to interop with it then there
isn't much choice.

> The namespace prefixes that are automatically added by the Serializer
> are in form ns<n> where n is the sequence number.
> So if any stub or handler adds a prefix of that kind there can be
> namespace prefix conflicts. This api change was aimed at avoiding this
> kind of conflicts.

Yes there is indeed such a risk .. the solution is to say that the
prefix given when registering a namespace is *desired* prefix. If
that prefix is already in use then an auto generated one can be used.
If its not in use, then there's no reason not to use it.

In any case, if the API existed before then removing it should be
done after lots of flags and warnings .. otherwise anyone who depended
on it is screwed. 

The suggestion Samisa made of "deprecating" old APIs before removing
is very good. Maybe doxygen supports something like the @deprecated


View raw message