|
-
Dec 5th, 2008, 06:21 PM
#1
Thread Starter
New Member
[2008] Program structure, multiple processes, serial
Using: visual studio 2008 w/ sql 2008
Background: We have created a program that creates an order consisting of tests that is sent to multiple analyzers via serial strings. The tests are then run through the analyzers and the results are sent back through serial and databased.
Problems: In order for the program to send the ordered tests or receive the results we have to have a toggle switch in order to specify which serial COM port to listen to.
Questions: Is having a 3-tier (UI - DB - Background Processes) program the best approach to this problem. If so, how would we structure the UI to communicate with the background processes constantly? Is multi-threading a better option?
Thoughts: We were considering converting our project into a 3-tier program. The user interface will have to send orders to the background processes. The background processes will be responsible for all of the serial data (business logic). Everything will be stored in SQL db. Need your advice. Thanks for reading, hope someone can help.
team sin2win
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|