Um... Guys... Did you read his post:
Quote: "I will be doing it in C++ since the server will be based on Linux/Unix(More likely Linux)."
Speaking of Which Soulman, FreePascal and Lazarus are SO perfect for this like C++ is. (You'd be pleasantly surprised how fast I [edit] ahem..excuse me..
YOU [/edit] can whip up a MySQL application in linux with FreePascal - its sweet.
)
And APEXNow....
Quote: "Installing this driver then allows you to create proper DataSets"
Proper? What is a Proper dataset? I figure anytime I run a SQL command or Stored procedure without a syntax error its "Proper". Can you elaborate...I'm confused. I think your suggesting that doing it Microsoft's way is "Proper" eludes that other way are not . I could totally be misunderstanding your slant on the use of the word proper admittedly but I think those kinds of sentiments are rubbish - placing Microsoft's "new fangled way" (of selling more software) as Proper is a stretch..especially considering the overhead of Microsoft's "new fangled way" versus a c++ approach using the NATIVE MySQL API for the database in question is absurd.
Have you seen some of the overhead of using MySQL with ODBC versus the Native MySQL Driver? Especially in a Linux Environment where MySql was originally written a honed/tuned for/on? How about some of the MySQL ODBC glitches it has when you start trying to pipe a bunch of MYSQL SQL commands over the wire via ODBC? (or local via loopback) MySQL's starting to get those ironed out - but it hasn't been there main focus because of the large number of users who just code to their native API.[edit]And I should have said that their ODBC is Pretty STABLE for basic SELECT queries - so its been good enough for most ODBC users[/edit]
I don't think its a question of what you may think is "proper" - I think its a question of his requirements for this application.
If he needs "database independance" - then he should consider writing directly to or using a help lib to get at the ODBC interface for whatever OS he's on... in this case linux... unlike Microsoft... there are a number of ways he can get at this.. and likely many ways to skin the ODBC cat going.
I stand by my previous statement
Quote: "Ok... for simple MySQL access - I'd code directly to their MySQL.dll (which talks natively to MySQL) and do it in a separate thread or make a multiplexor bit-o-code to do it. Both will work fine but the threading will give you more control of how much code is running and when in your main game thread.
"
and I think that Linux is the right choice for this type of web hosting/database combination. Even Apache/MySql (there are faster Web servers than appache... My own is the fastest I've seen yet - but no SSL or integrated PHP - must shell... you might [edit]
want[/edit] integrated PHP and SSL for security. I make programs and compile them right into web server (Its the fastest way to do web coding - no thunking, no extra stuff... just take the base WEBSERVER and add your special stuff to it and compile it as one application
so I personally don't need it - I don't use PHP much.... Anyways....
This config will be MUCH faster pound for pound = same hardware etc - than using Microsoft IIS, SQL server etc... plus it won't slow down once a week like IIS tends too. Apache and MySQL also TEND to run better in my opinion on linux from a speed persepective.
Consider LIGHTTP for Linux for this also...
Good Luck!