<script>var SECURITY_KEY = "918028cd79a5ba47e83e6ba68d036ca3";</script>
Really, this doesn't seem like a very hard problem to solve...couple lines of code...
See "Good Patterns & procedures to prevent CSRF":
EDIT: ...and after I was done typing the message above I returned to gmail and 15+ more requests has been fired off without me doing anything. The message took well under a minute to type. Seems like a lot of validation would have to be done.
EDIT: To answer your question of "are they doing some kind of lookup for each AJAX request?" Well of course, since they already have to look up a user's ID, account information, etc. based on the cookie they send.
Now maybe they are performing a lookup for each request but I just do not see how they can handle the load, or why they would want to given the alternative I just suggested. Google sends a ridiculous amount of data back to their servers during a Gmail session. I haven't examined the traffic extensively but open up a chat box in gmail and the Firebug console at the same time. Click anywhere in the chat box. See the request that fires off int he console? That happens EACH TIME you click ANYWHERE in the box. I guess they are doing some type of clicking heat map or something I don't know, but whatever they are doing it requires sending potentially 1+ AJAX requests per second for many users.
I am not knowledgeable enough to tell you how much is too much for a server/file system/database to handle quickly (~150 ms per request for millions of requests at once) so maybe the situation I just described is not as bad as I made it seem.
Currently, I keep a clean Opera installation solely for high-importance secure transactions, but I like some of the features that (I know, I have to trust them) Firefox extensions add to Gmail. I also don't want to be running Gmail through that clean Opera installation; I want to restrict my use of the latter to access to known sites and trusted content.