| View previous topic :: View next topic |
| Author |
Message |
DoT_PiTcH Contributor

Joined: 07 Aug 2002 Posts: 85
|
Posted: Tue Nov 08, 2011 9:17 pm Post subject: client / server |
|
|
when designing and developing a client/server app. would you recommend designing the server or client first or parallel with each other.
just trying to get out of adding a feature to the server and forgetting about it on the client or visa versa.
then comes the testing. if i develop the client first functionality testing cant be done really until the server can process everything being sent to it |
|
| Back to top |
|
 |
bornsoft Contributor

Joined: 19 Feb 2009 Posts: 113 Location: Germany
|
Posted: Tue Nov 08, 2011 10:25 pm Post subject: |
|
|
Hi,
nice to know that there is still someone working with VDS ...
Your question makes me smile, 'cause I know exactly what you mean
My suggestion is to take a paper and a pen and write down what features both, your client and your server should have. (Take you time for that.) When you implemented a feature you make a checkmark at your list and when it comes that you have a new idea, append it to your list.
To start with the server or client first depends on the protocol - if there are already clients for what you wanna do you can test with, you should start with the server and vice versa.
BTW:
If you like beta-testing: I'm working on a VDS-unit called "bsWinSock".
It allows socket-communication in VDS of any kind without the need of an external DLL like VDSIPP or VDSINET.
The project is in an early stage but TCP works quite well. UDP is not yet implemented completely.
I plan to make it open source 'cause I have not so much time at the moment and it would be pitty to let it go down the jordan.
So if you are interested you can PM me your email-address so I can send you the project.
Greetings
bornSoft
. |
|
| Back to top |
|
 |
DoT_PiTcH Contributor

Joined: 07 Aug 2002 Posts: 85
|
Posted: Wed Nov 09, 2011 3:08 pm Post subject: |
|
|
thanks for the reply, that's what i have started doing writing a list of what needs to happen. and unfortunately i must develop the server and client (in house app for management). but yes the VDS unit sound very interesting, i would be willing to implement it for testing when you get it where you want it.
p.s.
I love developing in VDS, i know pascal intermediately, i have about 20 hours of delphi training videos but for some reason, i fall back to VDS as im more comforttable with it. the only down fall is DB interaction. i know there are DLLs for actual DB. but delphi can do it from IDE |
|
| Back to top |
|
 |
Garrett Moderator Team
Joined: 04 Oct 2001 Posts: 2149 Location: A House
|
Posted: Wed Nov 09, 2011 5:25 pm Post subject: |
|
|
The last time I made anything in this manner was an Instant Message setup. I started with the server first to get some of the basic functions first, then started on the client to match up with the server. After that it was in tandem, add a function to the server, then hit the client up to match the server and repeated until I had it all done. _________________ 'What you do not want done to yourself, do not do to others.' - Confucius (550 b.c. to 479 b.c.) |
|
| Back to top |
|
 |
|