On Jan 29, 3:26 am, Maarten De Schrijver <[email protected]> wrote:
> Now, in my idea: wouldn't it be better, in the second step (page 2) to > just immediately persist the user submitted data to the SQLite database to > allow the user to continue the flow and to hand off the connection to the > remote CRM to another app/process/Celery/whatever after which I can (if > needed) update the user's data in de database? Yes, totally. I thought your app was going to be fetching data for client display. Since there's no need to present this data, you can totally just save it and process later. In your case, you could even run a cron script or something else periodically - nothing you have is time sensitive. Having worked with a lot of contests before, I'd suggest keeping a local cache of 'seen' email addresses. I'm always surprised at how many times people will try to enter duplicates. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
