I spent a year working on a multiplayer online game using Silverlight for the interface and Python for the backend (I actually used IronPython in Silverlight to make development easier)
Silverlight is very suitable for this, I would not be a serious online game in anything else. It already has 35% of the market, by the time you finish development, it should be high enough not to make much difference. For serious games, most people really do not mind installing a 4MB browser. If you just want to clone some asteroids, use the flash.
If I had to do this, I would put Python on the server, because it is the server technology that I understand most of all, but I think I would use C # on the interface and use JSON to transfer data.
The best advice I can give you:
- Use existing libraries and code as much as possible
- Do not think about performance prematurely
The hardest part is to finish the game, use the technology that you know well, and optimize your time, not the code. I hope you can do what I could not - finish the damn game :)
Edit
Regarding why I used C # if I had to do this:
IronPython had its advantages and disadvantages. It was great that I could share code files (constants, models, etc.) between the server and the client. Make changes and refresh your browser to see that it was awesome. Debugging was not as friendly as C #.
But in a way, this is a second-class citizen for C #, data binding does not work, and you cannot use IronPython classes in xaml. Download time was a problem, so I really spent a lot of effort to set up import in parallel across background threads to speed it up. Due to the second citizen status that uses xaml, I used the template language to generate xaml, as if it were html that really worked better than data binding, but python template languages did not work in IronPython, so I wrote my own ( next time.)
To enable sharing models, I had to write my own ORM. It was easy enough. But to pass them, I passed JSON and instead created an optimized binary format that worked between IronPython and Python. It was a different time.
In retrospect, I should not have been distracted by all these rabbit paths.