I'm curious about what good/best practice is when setting up an action that will be utilizing ajax updates. Let's say we are working with the users/index controller/action that will be listing out all the users in the system. The table of users will be updated via ajax as the user pages through the list.
Is it best to have 2 actions in the controller? One that sets up the whole index page and another (using just the ajax layout) that is doing the actual querying of the users? The latter being accessed by the former via requestAction() I ask because if only a part of a page is going to be updated, I would think that it would be best to seperate that part into it's own action. That way, I can minimize the amount of data that is coming back from the server using the ajax layout. Otherwise, the whole page would be refreshed. Or am I thinking about this the wrong way? thnx, Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
