>1) How often does the server receive a message for processing? (How many hits per minute or per second, etc)

The server would be very often perhaps 20 per minute.
The HTML help app whenever the user presses F1 so not so often.

>2) How long does the server processing take?
Probably about 5-10 seconds


>3) What is the required response time of results back to the originating application, or does the server actually send any results back?

30 Seconds response is exceptable but real time (or near) would be nice.


>4) If no result returned from the server actions to the client, what is the time sensitivity of the server doing what is requested?

The server could either make a change to some data which the user could see on
their screen or send an instant response. Both methods would be acceptable.
The HELP app just shows a web page.

i'm thinking I should use Sockets and TCP\IP for the server and HTML help app.
If it's the fastest. The messages shouldd be just a key and I don't want it polling with SQL frequently. I guess I'm looking for more info.

Thanks for the help.

>Same for the HELP application...
>
>
>>Hej!
>>
>>What is the fastest solution available and various advantages and disadvantages of using the following solutions for an application to recieve messages...
>>
>>Two scenarios:
>>
>>1) The server application runs a process that updates some data.
>> -Timer: A timer runs every so often and uses SQL to create a cursor of records to process.
>> -Com Server: instead of insterting the records in a table I make a call to the com server like oServer.DoStuff("keyvalue")
>> -Sockets: Use Windows Sockets Active X and TCP\IP or UDP to send the message
>>
>>2) HTML Based Help Application.
>>When the application is open I need to pass a key to the application.
>>Triggered by F1 in another application...
>>
>>It looks up the key in a table and displays the matching HTML file name.
>>
>>The application may remain open so like the above scenerio
>> -Timer: A timer runs every so often and uses SQL to create a cursor of records to process.
>> -Com Server: instead of insterting the records in a table I make a call to the com server like oServer.DoStuff("keyvalue")
>> -Sockets: Use Windows Sockets Active X and TCP\IP (localhost) to send the message
>>
>> -Win API: use the windows API to send a message
>> -VFP: use VFP to directly manipulate and call functions in another application...(Not sure if this can be done?)
>>
>>I'm looking for any advice or best practices advice or new solutions for the above two scenarios where the applications need to recieve messages from another application and respond. I appreciate any comments or advice.
>>
>>Thanks!
>>thanks