EGL and Ajax

Justin Taylor wrote:

1. I was operating under the assumption that a single server call would
be faster.
2. Jon Sayles was quite helpful and I have a large (> 900 slide)
presentation that he sent me, but in this case I am wanting to refresh
the current page (something similar to
http://www.ibmsystemsmag.com/i5/december07/developer/18780p1.aspx ).

A single server call may or may not be faster, depending on how much data is sent. For example, sending an array of 99 elements when only one is filled is obviously much slower than sending a single record. And you either have to create a huge array, large enough to hold the biggest set you will ever get, or else you have to code paging logic to handle the situation when there are more records than fit in the array. And at that point, you might as well just do a record at a time.

And while you know that I'm a big stickler for performance, in this case I think the control you get by sending one record at a time offsets any performance issues. Like I said in my earlier post, the call time is very, very short.

As to the tutorial, have you asked Jon for his Ajax tutorial? You should walk through that and understand the concepts of ajaxRefreshRequest and how that all works conceptually, and then I can give you specific pointers on how to get it to work with a table.

Joe