|
|
Posted by Dr. No on 03/06/07 01:58
met00 wrote:
> Dr. No wrote:
>> What you are attempting to do sounds like a bad design pattern, and
>> there is probably a better way to do it. There are two problems with
>> your idea.
>
> it's a bad design pattern, and it is supported by web2.0 (ajax) design
> patterns.
>
> take data from form in div -> ajax to server -> display second form (or
> add it to the current form on the fly) based on data in div -> ad nausium.
>
> welcome to the concept of the web browser as a programmable interface
> for client server acync communication.
In this case, I think the original poster was referring to using a popup
_window_, rather than a div, which I think is a bad pattern. I have fewer
objections to using a div in the circumstances described, but I think that the
tendency of inexperienced developers is to try the overly complex solution
before seeking the simple one.
I think there's a time an a place for asynchronous JavaScript, be it XML or JSON
based. There is a lot of potential for the technology, and I wouldn't consider
it in and of itself to be a bad design pattern. However, I don't think there is
a consensus yet in the developer community as to what best-practice is, and I'm
afraid that we'll see a lot of pressure being put on web developers over the
next few years to build AJAX applications in situations where the stateless
paradigm for web applications would be significantly more effective.
I had issue with your equation of AJAX with "Web 2.0". AJAX is a real-technology
stack, that is going to be with us for a while. Web 2.0 is a rather amorphous
buzzword that encompasses a number of things, some of which are better than
others. I think AJAX is good in either small doses, or in large doses in limited
circumstances when it is really well executed, such as Google Maps.
Personally, I'll be working with Web 1.8.6 until we see the release of Web
2.0.1. :^)
Navigation:
[Reply to this message]
|