Quote:
|
Originally Posted by Damilis
Hmmm. Work is boring so i have been brainstorming:
Idea: Now I understand that the idea has potential security problems not to mention the myriad of other issues that result from distributed computing, but what if....
...Someone where to alter the zone.exe compile so that it doesn't rely on an external config file (db.ini)/start arguments. aka, all the settings are internal internal and external IPs, db connection, db userid, db password, port numbers, etc. This would be done so that people can register to receive a customized zone.exe that they can execute on there own PC but have it log into a remote world.exe. This way a distributed style EQEmu server could be created.
Issues that I can see up front:
-The MySQL server would have to have a damn fast connection.
-The remotely located zone.exes would have to have a decently fast connection.
-Even hard coding the settings still presents a security risk for the DB.
-Uptime now becomes less quantifiable due to the expect large range of PCs the Zone.exes will be running on.
Okay... yalls turn... good idea? Bad idea? Idea that needs a little work, but could work?
|
I think it would be Very laggy even with a dedicated sql and world server.
the loading time for a zone would be thu the roof.
I might be wrong but it seems like a lot of wasted bandwith for nothing to me.
and theres no real reason to have off site zones they take up very little cpu and memory unless it's a big zone like GD.
now if you get a memory leak... they do lock up the server.