Steve Ulrich wrote:
Hi!
Some thoughts should be spend how the additional atomic operations can be
triggered and how to hint that to new users.
I know that they can be accessed via the AttributeMap, but this isn't stated
somewhere explicitly. Letting only the simple get/set/remove methods at the
IoSession will confuse new users, especially if they are documented as they are
at the moment.
The current documentation is most certainly something we have to
improve. The fact that we have so many useless methods slowed down the
documentation effort too.
So I buy your point of view : if we keep the API small, we have to
increase the level of documentation.
So either remove them completely, or just state that they are convenience methods and what to do
"normally" (e.g. "This is a convenience method for
getAttributeMap().getAttribute(Object key)"). Maybe a link to the IoSessionAttributeMap-method
would be nice, too.
We may expose the inner data structure, but I'm not sure it's a good
idea. IMO, the way it's stored (ie attributeMap) should remain hidden to
the users.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
