On Sat, 2008-10-04 at 13:38 +0100, Ashley Sheridan wrote: > On Sat, 2008-10-04 at 13:48 +0200, Nitsan Bin-Nun wrote: > > It depends how much stuff you have in the first div, it there are a lot of > > images and the user will have to load them again (in case there is no cache) > > and you care for the traffic those images cost - it would be better to use > > AJAX. > > > > But generally - they both okay, I personally would use reload of the whole > > page just because of the time it would take me to develop it with ajax ;) > > > > HTH, > > Nitsan > > > > On Sat, Oct 4, 2008 at 12:10 PM, Alain Roger <raf.news@xxxxxxxxx> wrote: > > > > > HI, > > > > > > i'm currently working on some web application and i would like to know what > > > is the best way to do what i want. > > > basically like all application i have a menu and based on selected item > > > menu > > > i want to display a page (basically 50 % of this new page is DB > > > result/grid. > > > > > > As usual i have 2 divs, one for the menu one for the content of DB to > > > display. > > > i would like to know if it's not better to use AJAX to load the content of > > > the second div (DB result and other stuff) instead to every time load a new > > > page which load menu and content of DB ? > > > > > > what are your experiences on such thing ? > > > thx. > > > > > > -- > > > Alain > > > ------------------------------------ > > > Windows XP SP3 > > > PostgreSQL 8.2.4 / MS SQL server 2005 > > > Apache 2.2.4 > > > PHP 5.2.4 > > > C# 2005-2008 > > > > Also, it depends on who you think will be visiting the site, as an > increasing number of people browse the web with devices that have no > JavaScript capabilities, so they wouldn't be able to use an Ajax site. So just engineer the AJAX so it falls back to traditional full page reload when JavaScript is disabled. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
