Hi, Perhaps you can consider using JSON as the format to be process, which tend to be smaller in size. And you can leverage the native json_decode() from PHP engine. More information on JSON format with Google Data API -
http://code.google.com/apis/gdata/json.html Hope that helps, Austin On Thu, Jul 10, 2008 at 10:14 PM, Tom <[EMAIL PROTECTED]> wrote: > > Actually, since it was the CalendarEventFeed object that was making > the big memory hit (and not the string of the feed's XML), I ended up > just writing some code that parsed the XML string into an array that > only had the fields I needed. This decreased the memory usage enough > for my purposes, but I'd still be interested in hearing if there are > any ways of doing this custom projection thing, since it'd still help > slim down memory, and might just be nice to know for future reference. > > -Tom > > > > On Jul 10, 10:05 am, Tom <[EMAIL PROTECTED]> wrote: > > Is there any way to specify exactly which fields are returned in a > > calendar feed? I'm working with the PHP library and am running into > > some issues with memory size from unnecessary fields in a large feed. > > (None of the predefined projection types like "full-noattendees" and > > "composite" really fit what I need; they all either have too few or > > too many fields.) > > > > Any ideas on how to do this? I'm fine with modifying the Zend library > > to pull it off--I've already been doing that a little bit anyway. > > > > Thanks, > > Tom > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
