[google-appengine] Re: Sharing an app between different Google apps domains

2009-09-07 Thread tyoc

Im interested in know when people would be able to use their hosted
mails in google like an equivalent for a google account, for example
to join reader... or enter different appspot apps.

So like I see, if I do an application it will be a shared resource, I
mean, that is the way that for example the services for: calendar,
documents, sites and other services of google are implemented?


On 10 ago, 03:30, "Nick Johnson (Google)" 
wrote:
> On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
>
> > Heres the background - I'm developing anapp, lets say accounting
> > software, that I'd like to sell to organizations using Google Apps.
>
> > How do I manage deployments? If I just create oneapp, it is possible
> > for all my clients to import it into their dashboard and use it like
> > their ownapp?
>
> Yes, though currently their users will have to have Google accounts
> (you can create a Google account for any email address by going 
> tohttps://www.google.com/accounts/NewAccount) in order to sign in, since
> you can only set yourappto work with Google accounts or one 
> specificdomain'saccounts. Alternately, you can work around this limitation by
> using OpenID, but this is rather cumbersome.
>
>
>
> > I don't want to create, maintain and update a separateappfor each
> > and every one of my customers... how can I share theappwith my
> > client domains keeping a separate datastore and auth setup for each of
> > them?
>
> If you're using the approach outlined above, you'll need to enforce
> separation in your datastore yourself - for example, by restricting
> records based on the Host header the site is accessed through, and/or
> the hostname of the user who's logged in. One way to do this is with
> Hooks:http://code.google.com/appengine/articles/hooks.html
>
> -Nick Johnson
>
>
>
> > Sudhir
>
> --
> Nick Johnson, Developer Programs Engineer,AppEngine

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Sharing an app between different Google apps domains

2009-08-14 Thread Nick Johnson (Google)
On Thu, Aug 13, 2009 at 5:43 PM, Elias Torres  wrote:

>
> On Aug 10, 4:30 am, "Nick Johnson (Google)" 
> wrote:
> > On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
> >
> > > Heres the background - I'm developing an app, lets say accounting
> > > software, that I'd like to sell to organizations using Google Apps.
> >
> > > How do I manage deployments? If I just create one app, it is possible
> > > for all my clients to import it into their dashboard and use it like
> > > their own app?
> >
> > Yes, though currently their users will have to have Google accounts
> > (you can create a Google account for any email address by going
> tohttps://www.google.com/accounts/NewAccount) in order to sign in, since
> > you can only set your app to work with Google accounts or one specific
> > domain's accounts. Alternately, you can work around this limitation by
> > using OpenID, but this is rather cumbersome.
> >
> >
> >
> > > I don't want to create, maintain and update a separate app for each
> > > and every one of my customers... how can I share the app with my
> > > client domains keeping a separate datastore and auth setup for each of
> > > them?
> >
> > If you're using the approach outlined above, you'll need to enforce
> > separation in your datastore yourself - for example, by restricting
> > records based on the Host header the site is accessed through, and/or
> > the hostname of the user who's logged in. One way to do this is with
> > Hooks:http://code.google.com/appengine/articles/hooks.html
> >
>
> If I'm using my own registration/authentication can I just point any
> domain (naked or dressed) to my appspot app and the Host header will
> always be there?


Correct, except that this doesn't change the fact that App Engine doesn't
currently support 'naked' domains.

-Nick Johnson


>
>
> -Elias
>
> > -Nick Johnson
> >
> >
> >
> > > Sudhir
> >
> > --
> > Nick Johnson, Developer Programs Engineer, App Engine
> >
>


-- 
Nick Johnson, Developer Programs Engineer, App Engine

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Sharing an app between different Google apps domains

2009-08-13 Thread Elias Torres

On Aug 10, 4:30 am, "Nick Johnson (Google)" 
wrote:
> On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
>
> > Heres the background - I'm developing an app, lets say accounting
> > software, that I'd like to sell to organizations using Google Apps.
>
> > How do I manage deployments? If I just create one app, it is possible
> > for all my clients to import it into their dashboard and use it like
> > their own app?
>
> Yes, though currently their users will have to have Google accounts
> (you can create a Google account for any email address by going 
> tohttps://www.google.com/accounts/NewAccount) in order to sign in, since
> you can only set your app to work with Google accounts or one specific
> domain's accounts. Alternately, you can work around this limitation by
> using OpenID, but this is rather cumbersome.
>
>
>
> > I don't want to create, maintain and update a separate app for each
> > and every one of my customers... how can I share the app with my
> > client domains keeping a separate datastore and auth setup for each of
> > them?
>
> If you're using the approach outlined above, you'll need to enforce
> separation in your datastore yourself - for example, by restricting
> records based on the Host header the site is accessed through, and/or
> the hostname of the user who's logged in. One way to do this is with
> Hooks:http://code.google.com/appengine/articles/hooks.html
>

If I'm using my own registration/authentication can I just point any
domain (naked or dressed) to my appspot app and the Host header will
always be there?

-Elias

> -Nick Johnson
>
>
>
> > Sudhir
>
> --
> Nick Johnson, Developer Programs Engineer, App Engine
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Sharing an app between different Google apps domains

2009-08-11 Thread Nick Johnson (Google)

On Tue, Aug 11, 2009 at 5:31 PM, Ben Nevile wrote:
>
> Hi Nick,
>
> Hooks are cool!  Thanks for bringing my attention to them.
>
> Can you expand a bit on how one might handle a multi-account scenario
> using hooks?  All I can imagine is a datastore hook that is smart
> enough to insert the proper filter on a query before it is executed --
> is that what you had in mind?

Yes, that's about the size of it. On puts, you add the 'domain'
property to all entities automatically, and on query, you
automatically add the required filter.

-Nick Johnson

>
> Ben
>
>
> On Aug 10, 1:30 am, "Nick Johnson (Google)" 
> wrote:
>> On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
>>
>> > Heres the background - I'm developing an app, lets say accounting
>> > software, that I'd like to sell to organizations using Google Apps.
>>
>> > How do I manage deployments? If I just create one app, it is possible
>> > for all my clients to import it into their dashboard and use it like
>> > their own app?
>>
>> Yes, though currently their users will have to have Google accounts
>> (you can create a Google account for any email address by going 
>> tohttps://www.google.com/accounts/NewAccount) in order to sign in, since
>> you can only set your app to work with Google accounts or one specific
>> domain's accounts. Alternately, you can work around this limitation by
>> using OpenID, but this is rather cumbersome.
>>
>>
>>
>> > I don't want to create, maintain and update a separate app for each
>> > and every one of my customers... how can I share the app with my
>> > client domains keeping a separate datastore and auth setup for each of
>> > them?
>>
>> If you're using the approach outlined above, you'll need to enforce
>> separation in your datastore yourself - for example, by restricting
>> records based on the Host header the site is accessed through, and/or
>> the hostname of the user who's logged in. One way to do this is with
>> Hooks:http://code.google.com/appengine/articles/hooks.html
>>
>> -Nick Johnson
>>
>>
>>
>> > Sudhir
>>
>> --
>> Nick Johnson, Developer Programs Engineer, App Engine
> >
>



-- 
Nick Johnson, Developer Programs Engineer, App Engine

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Sharing an app between different Google apps domains

2009-08-11 Thread Ben Nevile

Hi Nick,

Hooks are cool!  Thanks for bringing my attention to them.

Can you expand a bit on how one might handle a multi-account scenario
using hooks?  All I can imagine is a datastore hook that is smart
enough to insert the proper filter on a query before it is executed --
is that what you had in mind?

Ben


On Aug 10, 1:30 am, "Nick Johnson (Google)" 
wrote:
> On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
>
> > Heres the background - I'm developing an app, lets say accounting
> > software, that I'd like to sell to organizations using Google Apps.
>
> > How do I manage deployments? If I just create one app, it is possible
> > for all my clients to import it into their dashboard and use it like
> > their own app?
>
> Yes, though currently their users will have to have Google accounts
> (you can create a Google account for any email address by going 
> tohttps://www.google.com/accounts/NewAccount) in order to sign in, since
> you can only set your app to work with Google accounts or one specific
> domain's accounts. Alternately, you can work around this limitation by
> using OpenID, but this is rather cumbersome.
>
>
>
> > I don't want to create, maintain and update a separate app for each
> > and every one of my customers... how can I share the app with my
> > client domains keeping a separate datastore and auth setup for each of
> > them?
>
> If you're using the approach outlined above, you'll need to enforce
> separation in your datastore yourself - for example, by restricting
> records based on the Host header the site is accessed through, and/or
> the hostname of the user who's logged in. One way to do this is with
> Hooks:http://code.google.com/appengine/articles/hooks.html
>
> -Nick Johnson
>
>
>
> > Sudhir
>
> --
> Nick Johnson, Developer Programs Engineer, App Engine
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Sharing an app between different Google apps domains

2009-08-10 Thread Sudhir

Is there an ETA for that kind of sharing? The point of this idea is to
let the users of each organization use their custom domain based
Google Apps authentication, while saving me the trouble of managing
and updating a large number of app deployments.

Sudhir




On Aug 10, 1:30 pm, "Nick Johnson (Google)" 
wrote:
> On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
>
> > Heres the background - I'm developing an app, lets say accounting
> > software, that I'd like to sell to organizations using Google Apps.
>
> > How do I manage deployments? If I just create one app, it is possible
> > for all my clients to import it into their dashboard and use it like
> > their own app?
>
> Yes, though currently their users will have to have Google accounts
> (you can create a Google account for any email address by going 
> tohttps://www.google.com/accounts/NewAccount) in order to sign in, since
> you can only set your app to work with Google accounts or one specific
> domain's accounts. Alternately, you can work around this limitation by
> using OpenID, but this is rather cumbersome.
>
>
>
> > I don't want to create, maintain and update a separate app for each
> > and every one of my customers... how can I share the app with my
> > client domains keeping a separate datastore and auth setup for each of
> > them?
>
> If you're using the approach outlined above, you'll need to enforce
> separation in your datastore yourself - for example, by restricting
> records based on the Host header the site is accessed through, and/or
> the hostname of the user who's logged in. One way to do this is with
> Hooks:http://code.google.com/appengine/articles/hooks.html
>
> -Nick Johnson
>
>
>
> > Sudhir
>
> --
> Nick Johnson, Developer Programs Engineer, App Engine
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: Sharing an app between different Google apps domains

2009-08-10 Thread Nick Johnson (Google)

On Mon, Aug 10, 2009 at 9:02 AM, Sudhir wrote:
>
> Heres the background - I'm developing an app, lets say accounting
> software, that I'd like to sell to organizations using Google Apps.
>
> How do I manage deployments? If I just create one app, it is possible
> for all my clients to import it into their dashboard and use it like
> their own app?

Yes, though currently their users will have to have Google accounts
(you can create a Google account for any email address by going to
https://www.google.com/accounts/NewAccount) in order to sign in, since
you can only set your app to work with Google accounts or one specific
domain's accounts. Alternately, you can work around this limitation by
using OpenID, but this is rather cumbersome.

>
> I don't want to create, maintain and update a separate app for each
> and every one of my customers... how can I share the app with my
> client domains keeping a separate datastore and auth setup for each of
> them?

If you're using the approach outlined above, you'll need to enforce
separation in your datastore yourself - for example, by restricting
records based on the Host header the site is accessed through, and/or
the hostname of the user who's logged in. One way to do this is with
Hooks: http://code.google.com/appengine/articles/hooks.html

-Nick Johnson

>
> Sudhir
> >
>



-- 
Nick Johnson, Developer Programs Engineer, App Engine

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---