> > This is a necessary part of our workflow, and it does not make sense that > google would implement something via the GUI that cannot be done via the > API. Does anyone know why they did this? Wouldnt it make more sense to > wait until the API is working before having a feature available via GUI? > Now we have put all this work into the "group details", for hundreds of > groups, and the only way to see it / change it is to log in graphically? > to quote a prior post in this thread, this is very un-google-esque!!
Actually its entirely consistent with the way Google builds and updates services. They start by getting a basic service out there and then gradually improve and extend it in response to customer feedback. As has been noted elsewhere, there is a Groups API in the works. Yes, it sucks if you're trying to do something that isn't currently supported, but interim measures (like screen scraping) do exist if you need the functionality urgently enough. > Also, it is important for us to be able to parse thru the thousands of > archived group emails via python API. I see that this is not possible > either. Someone actually suggested adding a "silent user" and use IMAP w/ > filters. This is neither manageable nor scalable (we have 1000's of > groups) > As someone who has personally implemented this I can tell you that it is both manageable and scalable for tens of thousands of groups. We didn't use filters, instead opting to expose a search facility built on the back of X-GM-RAW search extension. Cheers, Rob. -- You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" 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-apps-mgmt-apis?hl=en.
