Architecture for Google Wave applications.

I’m designing an application for Google Wave, which interacts with the user. The following is the considerations that I have for how the architecture of the application works best.

The application that I’m planning on should consist of a Robot which interacts with the user. The other part of the application should be a web application where users can configure how the robot should interact and view status from the waves. There should also be some analytics capabilities. The backend application needs to be rather a little complex to fulfill the requirements.

The most convenient way would be to use appengine, since it is the place that is mostly integrated with Google Wave currently. Continue reading Architecture for Google Wave applications.

Bookmark and Share

Debugging Wave Robots

Debugging robots made in Google Wave can be a little difficult because it can only be tested on the server and it can be difficult to see how it is sent.

A way I have found is quite useful is to use the app engine log. On the log tab select “Requests only” and then see that data being sent to the robot. It is this data the robot can see, if it is not here then the robot API is not receiving the data.

I hope this help you debug and get at better understanding of your robot.

Update 19 aug 2009: If you want to format the JSON try the JSON formatter.

Bookmark and Share