Hi Dw.
I'm a bit stuck with a lot of confusion here.
I'm developing a client/server applications which communicates to each other, my project is a multi-thread based and I'm currently using MS Access and database but I have hit a very challenging problem as this was the wrong database to use at first due to its limitations.
My program uses signals(predefined messages) to perform the appropriate task to make a very simple example to login to your account you need to fill in the username and password and click login button.
The client will send: LOGIN:<txtusername.Text>:<txtpassword.Tex>
using LOGIN
as signal a server first check the signal and go to appropriate code for that signal so that it will perform the desired task. As to this sample, the application will try to login.
Now there is another part which keep sending the data retrieval signal after or in every 600 interval. So by doing so this courses the server to reach the maximum MS Access database connection limit by just one client, so I was adviced to move to MySQL server.
But upon doing some research I get confused more and more. First I think I need a proper explanation or clarification of the differences between:
MySQL
MySQL Server
MySQL Client
And to what each do, I mean its purpose and which one exactly I can use.
Upon the research I found out that MySQL consist of both Server and Client. Now if I download and use this will I have to add it client to my Client app, add its server to my server side app?
If I have MySQL Server would I still need my Server application?
I'm a bit lost with MySQL and I've just decided to get some more clarification on this and that does this comes with its own database?
What is the difference from these to that, that comes with WAMP server/LAMP server?
How can I adopt this to my application, what is it limitation, how many simultaneous activities can it handles because my application as I've said is currently multi-thread and will have extremely high traffic volume 24/7 where the data will be retrieved,updated,created now and then as clients uses the application, what more to look for.
I have the thread where I was advised to change to MySQL and you can see what problem we were talking about at: https://www.daniweb.com/programming/software-development/threads/504300/prevent-socket-clients-from-freezing-gui