Ok, got the difference. Now being a new bie to AJAX, what are the best techiques that should be used to design a well designed web app ? Again, my page has to show the new data thats being added to database. Frank told about creating a "timed AJAX event". Where can I get more details regarding that ? Again will it be possible /scalable for 2000 concurrent users ? Thanks
Adam Ruggles <[EMAIL PROTECTED]> wrote: The difference between using AJAX and just refreshing a page is a well designed AJAX application sends over just the information that is needed. For a JSP/HTML page refresh you're sending more data over the line. The key here is a well designed AJAX application. Maya menon wrote: > Thank you both for your responses. > > So AJAX is the technique I should refer. Anyone know of any examples / > somethings. > > Also, my colleague asked me this question when I talked to him about a "timed > AJAX event". Why cant we simply refresh the jsp page ? Why should we use AJAX > ? so, whats the real advantage of using an AJAX timed event to a normal > JSP/HTML refresh ? > > Maya > > Musachy Barroso wrote: > The div tag when used on the ajax theme, has a timer that will make it > refresh its content from the url specified in the "href" attribute, examples > available in showcase and here: > > http://struts.apache.org/2.x/docs/ajax-tags.html > > musachy > > On 2/28/07, Frank W. Zammetti wrote: > >> Well, if you can live with not literally "pushing" to the client, this is >> the sort of application AJAX was made for. Have a timed event, every few >> seconds maybe, whatever your tolerable definition of "real time" is, that >> makes and AJAX request to check for new data and display it when found. >> Pretty easy. >> >> Have a peak at the AjaxParts Taglib (APT) in Java Web Parts (JWP): >> >> http://javawebparts.sourceforge.net >> >> http://javawebparts.sourceforge.net/javadocs/javawebparts/ajaxparts/taglib/package-summary.html >> >> The benefit is that it will allow you to do this, since it has a timed >> AJAX event function, and will save you from having to write any Javascript >> yourself (most likely). >> >> Whether you go with APT or not, AJAX is probably the first thing you want >> to look at. >> >> Frank >> >> >> -- >> Frank W. Zammetti >> Founder and Chief Software Architect >> Omnytex Technologies >> http://www.omnytex.com >> AIM/Yahoo: fzammetti >> MSN: [EMAIL PROTECTED] >> Author of "Practical Ajax Projects With Java Technology" >> (2006, Apress, ISBN 1-59059-695-1) >> Java Web Parts - http://javawebparts.sourceforge.net >> Supplying the wheel, so you don't have to reinvent it! >> >> On Wed, February 28, 2007 3:54 pm, Maya menon wrote: >> >>> All, >>> >>> Have a design issue here. We have a web based application and have >>> >> 2000 >> >>> concurrent users. The requirement is: when new data comes on Oracle >>> database for users this data has to be sent to the online users on a >>> real time basis. Someway, the real time data needs to be pushed to the >>> users without the client doing a reload/refresh etc. >>> >>> What technologies can be used here ? Can anyone provide me some >>> suggestions ? >>> >>> The users login to the application using a web page, this is a web >>> >> based >> >>> J2ee application using struts, Oracle database. >>> >>> Thanks, >>> Maya >>> >>> >>> --------------------------------- >>> Any questions? Get answers on any topic at Yahoo! Answers. Try it now. >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > --------------------------------- Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
