This thread makes me think even more that using gData in this situation is a mistake on googles part for multiple reasons.
It's the one thing in the mix that has a proprietry brandname on it regardless of it being a valid extension. So far CakePHP says they won't develop wrappers for gData, while here we see gData not being able to support the needed features without further extension. This gData issue could be the one thing that pushes some serious open source developers away. While using more open (unbranded) standards in it's place would make all these developers much more comfortable. Maybe googles main concern other then promotion of it's products/ formats here is this issue of having the same fields available on different containers and trying to lock that down. Could be advantagious to them to bite the bullet and use an open standard at this stage rather then findout it's considered evil or doesn't provide enough functionality down the track. Don't get me wrong, I hate opensource, I'm no fanboy in that department...... Just think this has to be 100% open from the start or we'll all be switching to another solution which is 100% open in 6 months time. -Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Container Developers" 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/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
