Bob Ippolito wrote: > The answers to these questions really depend on the dataset. If your > dataset is very large, you definitely don't want to fetch the whole > thing. If it's very volatile, you want to fetch it often, etc.
That's good to know. It's neither large nor volatile. 2.5k records at most. What slows things down currently is that I do several evaluations and JOINs on each record (to determine status of products and find related data). While going through the MochiKit examples I realized I can use MochiKit.Async to, as they say, "facilitate the 'half a second' live updating". So instead of doing a call (or paring down) on each keystroke just wait a 1/2 or 1/4 second. That might almost completely solve my speed issue. > You > should also consider security when deciding which pieces of the > dataset to send -- you definitely don't want to make it possible for > one customer to start reading another customer's data without explicit > permission. Sorry. I should have mentioned that this is geared towards the administration side. In the future it will be cool to roll this out to customer side though. > JSON is much easier to work with than XML, but sometimes it's > appropriate to just send HTML fragments since it is higher performance > (but you trade client-side flexibility for that). Sometimes this > decision depends what platform you're using on the server-side. I will be using LAMP. > In general, I'd suggest doing whatever is easiest to make correct > first, and then optimize it for latency/performance later (if it turns > out that you need to). That may be what I need to do. Thanks for your input! Chris. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
