Thanks guys Michael, that link is very helpful. I got the numbers a bit mixed up, it should be around 25 result items each made up of 12 elements with around 12 pieces of information from db/json. - so yes, 300 elements total.
If you don't mind me asking, I'd like you guys to give me your opinion on what I'm doing at the moment. I'm making a search page that has filters and the way I have it set up, I use jQuery to retrieve filter values and pass them along via AJAX to the server. The server takes these values, stores them in a session then outputs the results, which then is html()'ed to my results DIV. (I'll be switching to JSON) What do you guys think? Currently the whole search page is a bit javascript dependent (both the actual input/manipulation of filters and the instant update of the results). Should I be really worried about people who have javascript disabled? Thanks! On Sep 30, 4:34 pm, Michael Geary <m...@mg.to> wrote: > 25 x 12 sounds closer to 300 elements? Either way, it's easy to generate > that much stuff in JavaScript and get good performance, if you're careful > about how you write the code. Here's a post with some tips and optimized > code for a similar task: > > http://groups.google.com/group/jquery-en/msg/121203c4216c34ee > > If you follow the basic pattern in that code it should be plenty fast. > > You could post the specific HTML you want to generate along with the JSON > format you plan to use if you have any questions about how to make it go > fast. > > -Mike > > On Wed, Sep 30, 2009 at 9:01 AM, Toaster <mr.toas...@gmail.com> wrote: > > > Thank you for your reply James > > > In regards to the JSON vs HTML, would the browser have any problems > > creating 25 results items each with 12 pieces of information from > > JSON? (it'd be more of less 120 elements being appended)
