John, Per RFC1855 Please use bottom posted replies when posting to an email list. Thanks > On Tue, Oct 28, 2008 at 6:35 AM, dhhs <[EMAIL PROTECTED]> wrote: > > Hello Erik, > > Seems I'm trying to do something similar for the agency I'm > > volunteering for (non profit). > > > We want to have a single calendar that people must log in to see. I'm > > liking google calendar, but I'm trying to make it secure (iframe > > dosen't do it, of course) > > > The viewers need to not be able to share this calendar with others > > with a simple link. > > > Thinking about your project... > > Can you have two calendars, one shared, the other one private. I'm not > > sure if there is a way to parse one with the other so that only some > > projects show? Just an Idea. > > > Lewis. On Oct 28, 12:05 pm, "John Lockwood" <[EMAIL PROTECTED]> wrote: > if you restricted access to the page via standard means(password protected, > or some other authentication code). Then you can use server-side code(like > php) to access the calendar data via it's private URL. This way the end user > would not have be able to see the private url. > > -John John, Are you saying that the server side code would be running on Google's server or some private server that Erik has?
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
