Hey Ryan,
Thanks for the quick response. We would fully expect that a user may be logged into Google for any number of your other products and would expect Authsub to "just work" for us in that case. I'm not sure if there are backend considerations for your implementation around that but we would be looking to authenticate and have a valid session token for use by our application. As for setting the context just prior, that is open to a disconnect based on the user. An interruption can create the disconnect in terms of time and windows and then we're dealing with user frustration because users demand context "Why am I answering this challenge?". I also don't expect us to be alone in the use of Authsub so other Authsub prompts could be near in terms of timing, better to have the ability to guide the user a little, right in that window. Regards, Derek. www.calgoo.comHey Ryan, Thanks for the quick response, I haven't seen this posted to the group so let me know if that will be the case and I'll drop this reply in there as well. We would fully expect that a user may be logged into Google for any number of your other products and would expect Authsub to "just work" for us in that case. I'm not sure if there are backend considerations for your implementation around that but we would be looking to authenticate and have a valid session token for use by our application. As for setting the context just prior, that is open to a disconnect based on the user. An interruption can create the disconnect in terms of time and windows and then we're dealing with user frustration because users demand context "Why am I answering this challenge?". I also don't expect us to be alone in the use of Authsub so other Authsub prompts could be near in terms of timing, better to have the ability to guide the user a little right in that window. Regards, Derek. www.calgoo.comHey Ryan, Thanks for the quick response, I haven't seen this posted to the group so let me know if that will be the case and I'll drop this reply in there as well. We would fully expect that a user may be logged into Google for any number of your other products and would expect Authsub to "just work" for us in that case. I'm not sure if there are backend considerations for your implementation around that but we would be looking to authenticate and have a valid session token for use by our application. As for setting the context just prior, that is open to a disconnect based on the user. An interruption can create the disconnect in terms of time and windows and then we're dealing with user frustration because users demand context "Why am I answering this challenge?". I also don't expect us to be alone in the use of Authsub so other Authsub prompts could be near in terms of timing, better to have the ability to guide the user a little right in that window. Regards, Derek. www.calgoo.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
