The best way to think of the version tag in capabilities.xml, is to use it as a tool to mark the milestones in your robot's life cycle. Therefore version 1 for instance will correspond to hello world, and version 2 will correspond to a new capability that you may add such as name="document_changed", etc. Also, it is a good idea to keep the version in capabilities.xml same as version number in appengine-web.xml just to make things simple, though this is not required. Note that Google App Engine will allow you to deploy a single app 12 versions only, so you will have to delete the unneeded versions there.
Popular Recent Articles
-
I have noticed a very unsettling statistic on my blog. This prompted a fascinating question about AI, blogs' future, and maybe even the... -
O'REILLY 201 0011 031 10110100180 000110111 01100041 001100010010000 5011011001010 1101110011 000100000 00000 10 1000012 Escaping the Bu... -
Installation of Java on Pi is easy, you can ssh to your Pi remotely and just execute: pi@raspberrypi ~ $ sudo apt-get update && su...
-
Epiphany is one of these interesting words that can mean so much. For me it means the crossroad where I chose the road less travelled. The r...
-
"Learn how to write, story-tell, or give up, you will not make a mark otherwise" ~ Greg Isenberg View on Amazon book Storyworthy:... -
On the mobile, the page is hard to read so I am including a LINK to Google document ...
-
How to Win Friends and Influence People: Updated For the Next Generation of Leaders by Dale Carnegie "The Only Book You Need to Lead Y... -
At some point, each application will have to perform some logic based on different cases. extract your CONSTANTS extract your logic into a s...
-
I progressively cut my hair shorter and shorter. Now, I just came back from the swimming pool with Lili, so it is a mess.
