I think that good writing sets a clear context and purpose up front. I’m no journalist, but it seems that when presenting a solution (and your original post is a valid solution) the application of or use case for the solution should lead. Here is the problem that I am trying to solve.

Cheers and keep up the good work.

I completely understand why you chose GAE and appreciate you showing the abilities to communicate across multiple collaboration platforms from a GAE driven application. As someone who is just beginning to dive into GAE I definitely appreciate seeing an integration example like this.

On Dave’s defense, he is not the only person who had that reaction from Salesforce.com. When I saw your post, I loved the fact you were addressing an integration problem, using OAuth and featuring Chatter, which you obviously liked, but at the same time I was extremely puzzled as to why you needed to add a hop to the solution. Some integrations do not need to be external as there are built in features that allow you to solve the problem in place, some do. My analogy is email integration. Thus, the question becomes what is featured in the blog and whether it may be misunderstood as if the platform was lacking a feature where it did not. Perhaps it explains the reaction.

However, the convergence of 3 APIs in the cloud using OAuth is a pretty powerful tool to have in your tool belt. I totally get the future potential and appreciate the source examples.

It’s a tabbed related list feature but it always throws the error ‘XXXX’ is not a valid child relationship name for entity Opportunity whenever I try to add a related list XXXX to the code