Ah, I see.  In any case this doesn't require new tags.

Part of this is I'm not just talking about validation.  In fact I think
that's about the most pedestrian use of AJAX around!  It's the cooler kind
of things you can get away with like table sorting, like the example in my
article.  Not that there aren't 100 ways to do that ;)

Your right, the usual JS event handlers fire, but what you do then can get
interesting... for instance, do you need to call a function to construct
an XML document and send that?  Or construct a query string?  Or maybe
just call a URL with no parameters?  And then what happens when the
request comes back?  There is obviously a JS function to handle it, but
what does it do?

My proposal and the accompanying example seeks to answer those questions
with the typical "whatever is in this XML config file" answer.  There is
no way in the world I can account for every possible scenario, but I was
trying to put together a generic enough solution so that I could provide
many, if not most, of the most common usages and allow them to be used
just by playing with the config file.  Validation was actually one thing I
was NOT specifically going to deal with.  Maybe I should though.

-- 
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

On Mon, April 18, 2005 3:37 pm, Jason King said:
> Frank W. Zammetti wrote:
>
>>You lost me Jason... what extra tags are you referring to?  My proposal
>>specifically didn't require any new tags, only additions to the existing
>>ones.
>>
>>
>>
> You previously said:
>
>>>>why not just modify the existing
>>>Struts tags to have some at least minimal AJAX functionality?  But what
>>>does that really mean? Simply put, instead of calling some Javascript
>>>function on the client in response to, say, the onClick event of a
>>> button,
>>>we instead call a server-side process, get a response back and update
>>> some
>>>part of the page.
>
> My thought is you'd call normal js events anyway.  The js events would
> call xmlhttprequest.
> That way we continue to use the same taglibs without any changes
> necessary.  My though is that an HTML <input> tag doesn't need to know
> whether its being validated by pure javascript or javascript +
> xmlhttprequest or <fill_in_the_blank>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to