1. Hosted game servers would probably have to be authorised on a source-code basis, and would probably have to be compatible with the grexengine containers.
However, it might be possible to write a generic simple fast server like Herk's stuff (or even, depending on his interest, actually use Herk's stuff
) and functioned somewhat like an "online HashMap" - i.e. developers/game-authors get to put data in, and pull it out, but not to launch executable code on the server. This way, security concerns are irrelevant (modulo suitable hardening of the server side), and as long as authors didn't mind doing their logic client-side they'd get both a free server AND avoid having to write all the networking code. Herk, if you have any thoughts on this, email me. I don't know enough about your stuff to know how easily it would function as a data-passing-only system.
2. Kev, when you say "NO FORUMS", I take it you are speaking in CMSese? I.e. CMS's tend to have two types of forum (usually the same engine but different parts of the site). One is a traditional free-for-all forum like this, the other is a "commentary"/"discussion" where the site maintainers can embed a mini-forum in any page, purely to discuss what's on that page.
I thought one feature people wanted was to be able to comment on and review games posted on the site, so these "embedded mini-forums" would seem like a wishlist feature?
Sadly, it seems the free CMS's today are still mostly written by trendy bloggers who know little about CMS's in the field, other than adding fancy features. So they haven't got their heads round really basic stuff like the importance of fine-grained access control - and it seems none of the really nice ones would allow mini forums on each page with a different unique named user as admin for each different mini forum. This is trivial stuff, and it's deeply depressing that so many CMS's don't even "get" this generic concept
. (although there are some that do, they seem to have other problems instead
Leaning more and more towards building a new one from scratch...Yuk.
3. AFAICS SlashCode etc is far too simplistic / narrow focus, and would provide nowhere near enough features
. And there appears to be only one CMS based on servlets. Worse, it's *extremely* hard to find ISP's that will host servlets (compare to the number that will host LAMP!) and they have no inherent benefit AFAICS, at least for this. If we have to have a JVM, there are much much better things to be running than servlets