Help in making Internet Cafe Timer
-
Hello Experts, I would like to ask a few guidelines in making an internet cafe software, I am kinda confuse if where should I start first. Do I need to start from the client part or the server part. I am planning to use vb.net and sql server/ms access for the database since I have use it in my previous project. I have created a project using vb.net and sql server in my past project and I wanted to try higher steps by doing network software. Any suggestions to help are kindly appreciated. Thanks in advance, DAN
-
Hello Experts, I would like to ask a few guidelines in making an internet cafe software, I am kinda confuse if where should I start first. Do I need to start from the client part or the server part. I am planning to use vb.net and sql server/ms access for the database since I have use it in my previous project. I have created a project using vb.net and sql server in my past project and I wanted to try higher steps by doing network software. Any suggestions to help are kindly appreciated. Thanks in advance, DAN
I would suggest you start by writing down your specifications and how he timer will be used. Then what should be client and server will likely be obvious.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Hello Experts, I would like to ask a few guidelines in making an internet cafe software, I am kinda confuse if where should I start first. Do I need to start from the client part or the server part. I am planning to use vb.net and sql server/ms access for the database since I have use it in my previous project. I have created a project using vb.net and sql server in my past project and I wanted to try higher steps by doing network software. Any suggestions to help are kindly appreciated. Thanks in advance, DAN
In additional to Walt's advice, for technology I would certainly be using SQL Server. You could start with SQL Express (its free) and upgrade when necessary much easier than starting with Access. As for language, and without starting a religious debate, IMO C# would be more appropriate. I believe there are more and better code samples available for you to learn from. Also since most network applications were, or still are, written in C++, the code is of better quality and it would be easier to translate to C# rather than VB given the similarities in syntax and structure between C++ and C#.
I know the language. I've read a book. - _Madmatt
-
In additional to Walt's advice, for technology I would certainly be using SQL Server. You could start with SQL Express (its free) and upgrade when necessary much easier than starting with Access. As for language, and without starting a religious debate, IMO C# would be more appropriate. I believe there are more and better code samples available for you to learn from. Also since most network applications were, or still are, written in C++, the code is of better quality and it would be easier to translate to C# rather than VB given the similarities in syntax and structure between C++ and C#.
I know the language. I've read a book. - _Madmatt
Hello experts, Thanks for all the suggestion and helpfull reply. Although I am not that good in c++ since vb is the 1st language were I can use database on it I will give a shot on c++/c#. Thanks, DAN
-
Hello experts, Thanks for all the suggestion and helpfull reply. Although I am not that good in c++ since vb is the 1st language were I can use database on it I will give a shot on c++/c#. Thanks, DAN
I'll agree with Mark and Walt, but add my two cents worth. If I understand your question, you want a timer on the connections to an Internet Cafe application. I assume you want to charge for access by the minute, or some finite time chunk. You'll need to create a connection pool from which users "check out" connections for a period of time. To my thinking, the proper place to implement the timer is on the server side, as each connection is established. When a user pays the fee, a connection is enabled and the timer started. When the timer completes, the server is notified of the connection associated with it, and the server should suspend the connection and ask for more money. If the user declines, or fails to respond (having packed up and walked away), the server then closes the connection and returns it to the pool. As has been mentioned, with a project this (potentially) complex, you really need to develop a detailed specification first, even if just for your own use. You're going to get quickly overwhelmed by the details if you don't have a clear roadmap to follow.
Will Rogers never met me.