as you imply, there are probably at least two aggregation account-management architectures.
(1) submit customer data under your account; (2) customer's submit their data through your application. trade-offs probably include: (a) requiring (legal) permission to access customer data; (b) risking users creating bad content; (c) requiring customers to create a google-base account and then authorize your application to submit data on their behalf; (d) risking users denying you future access. the cost/benefit is rather difficult to assess without knowing more about what you want the user-behavior and end-result to look like. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" 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/Google-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
