Hi all, I was curious if anyone has ever gone the route of bench marking the potential of using cookies for temporary client-side persistence, versus using XHR + databases.
I'm continuing to write an application where I need to save some very rudimentary information for a client for up to a 24 hour window. Something such as if a client has clicked a particular list item. I'm wondering if it's even worth putting the extra stress on the network and involving database overhead for this -- or if I should just use cookies for a faster solution. Or are they a faster solution? Again, as a simple example, I'll have a list of stuff in li objects. If a user clicks on one, I need to store that persistence for 24 hours. They can also 'unclick' it by tapping again. I'm curious if there would be more overhead in CPU for cookie storage/retrieval versus XHR+database read/writes. Any opinions? Cheers, /sf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" 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/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
