What's wrong with having an asp.net web site as proxy between server and
clients? You are writing you wanted to design a browser based game, so
browser needs to be involved. If you want to do it in a "proper OOP way",
standalone asp.net site won't be of any good use, because it's stateless. So
it can act only as a proxy. If you want to avoid constant sql queries, a
solution I can think of would be to develop a windows service which would
host the whole OO infrastructure and propagate it as remoted objects via
..NET remoting. ASP.NET site would act as remoting client and interact with
the environment.
"Antimon" <antimon@gmail.com> wrote in message
news:1136146682.698408.150290@g44g2000cwa.googlegr oups.com...[color=blue]
> Hi,
> I am working on a browser based space simulation game. I think about
> two different architectures but i cannot decide,
>
> First one is to use and rdbms to store persistent world data. But i
> want to have the whole game universe in OOP way. So i thought i can
> have a stand alone application to manage the whole universe. Everything
> would be objects in heap and i can dump them each 30 mins to a binary
> file. This way seems to be the fastest way to access and alter data. Of
> course i will need to be very careful about stability (a crash can
> cause a timewarp in this scenario). But i can reach any object without
> worrying about sql query overhead. Since i need a http server, i will
> write my own into the server applicaiton or have an asp.net project
> which acts like a proxy between clients and server and this doesn't
> seem to be a good solution.
>
> It seems that using a rdbms with an asp.net project is the best way but
> i would like to find a solution to be able to do this in oop way.
>
> Any suggestions?
>[/color]
