KermMartian wrote:These are some very good points, but points I have addressed since I last posted here nonetheless.
Don't worry, I (obviously) read your forum. Nothing escapes my attention
1. gCn is the dev directory; gcn is the frontend dir
I know, I said "in your FTP". The dev nonsense is more interesting than the frontend, and besides
http://www.cemetech.net/gcn /
http://gcn.cemetech.net/ gives a 404.
2. you see c++ because I decided to go ixnay on Java and try C++ instead for reasons such as using tilp. Java didn't seem like a good option in the long run
Of course not. Java can't interface with the hardware, it requires your users to install the JVM, and it's awfully slow. A scriptkiddie could have told you that.
3. Sending stuff via headers IS how you post - the POST data is sent in the headers.
Ah, stupid me
Still, there's nothing difficult about opening up a direct connection and manually sending out the headers.
4. I'm doing a bit of rewriting of the backend; Kllrnohj and I chatted and decided to modify the underlying schema a bit. Now instead of doing all communications tasks, each current running host can ALSO act as a server; it's a bit more complex than that, but that's the basic idea.
You'll still need a central server to host the directory of servers. You're not going to pull this off with PHP Kerm
You'll need all the speed you can get to compensate for the propagation delays, and using VM's and scripting languages isn't helping in that sense. Besides, no offense, but your server is one of the slowest I've ever seen. It takes ages to load even the smallest files.
If your serious with this, my advice is to write a simple C program (less is more
) for the backend and give that to some people with high end servers/connections. Let the client (C++ is alright) attempt to connect to those servers in a preset order, that'll keep the network as centralized as possible. That's the easy part. Once you've got that up and running you have to interface between the C++ client and a calculator (you can forget about connecting more than one calc to a client) in such a way that it's actually useful. So you'll need to write a browser, an IM client, mods for every game you want to be able to play over the Internet...
All of that is doable, but it's a LOT of work, it's going to be SLOW, and hardly anyone is going to use it because it's freaking pointless when you're sitting behind a computer
Anyway, it's an ambitious project, and I'm curious to see how far you'll get with it.
Edit@CompWiz:
I was typing a very long reply about the structure of the Internet and all the neccessary steps to get something from your PC to mine, and then I accidentally pressed Ctrl+W instead of Ctrl+T. You'll have guessed that I use Firefox...
Anyway the gist of it is that the size of a packet doesn't matter...