The use of AJAX by the viewer is tailored for its need, which
is mostly changing map state, handling selection and getting toolip/hyperlink
information. It is not designed to be extentded by user code can extend. I
think that for adding new interactive elements to the viewer you would be
better off using your own mechanism, which is fairly easy to implement because
the XMLHTTP object does most of the work for you. You can see examples of use
of XMLHTTP in ajaxmappane.templ, for example in RequestHyperlinkData() and
viewer obviously has some existing infrastructure for handling client-server
interactions. I am planning on adding some interactive user elements such as
suggesting street addresses as the user is typing, etc.
I'd appreciate feedback on whether I should be
implementing my own parallel handling mechanism for this (either Atlas for .Net
or maybe one of the PHP JSON classes) or whether there is some reference for
plugging into the mechanism that the AJAX
viewer is already using.