Re: RPG and AJAX was->RE: How do I create a webpagethat....

Hey dude, YOU were the one who said, "The additional complexity isn't that
hard to deal with."  My point is that the additional complexity *IS* hard to
deal with -- in fact, it becomes very difficult as soon as you try to make
the interface as bulletproof as a 5250, or even a basic web page.  You're
going to basically be reinventing all of the asynchronous session management
that's already in the browser.

Note your own statement: "To allow them to be processed out of order...".
So now you have to start making design decisions based on the number of
fields you want to be processed simultaneously.  Otherwise, your interface
will have to single thread each request.  Probably not an issue when you
have a dedicated machine doing POC, but likely to cause some consternation
as you start to scale (and in turn most likely to show up in peak periods
when it can least be afforded).

I'm just saying.  AJAX ain't a bad technology in and of itself, but there
will be a LOT of bad implementations of it.

Joe


> From: Walden H. Leverich
> 
> >AGGGGGH!  This is horrible!
> 
> It's Ajax POC (Proof of Concept), it's not about making it pretty and
> bulletproof.
> 
> >Not to mention, how many sessions did I have open while I was doing
> that?
> 
> To allow them to be processed out of order you had a new one for each
> request. However, if we remove that and queue them up behind eachother
> there's only one. To prove it look at the session id that created the
> page and the one that handled each request.