Hi Sumitrishi,
I found a document on MSDN that gives you a description about the
differents modes you are refering to
a
href=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcstconnectmodeenum.asp;ConnectModeEnum/a
I hope this helps
Sincerely,
Feroz
Thanks Rolf that was pretty informative.Furthering my efforts I was
looking at the property node for connection interface I have a feeling
that if anything has to be done it should be done at the point when
the connection is made . There is this particular property called
'mode' and one of the
The server part is OK. I see the session handler opens a database, my
guess is there is something there that prevents parallell replies. If
you strip down the session handler to just reply with a string
generated in the handler; are things still not able to run side by
side? If it's not could you
I would have to try it ( I mean stripping of handler).
But I am not sure if I would be able to feel any difference until
unless the size of the string returned by the handler is of
considerable size and would make the other handlers wait.
As far as database is concerened I have the admin
I am trying to write a server program that caters to multiple clients.
The clients are being made to wait in turn when the data has to be
sent back to them; and that exactly is my problem. The requests from
client are handled by the server pretty much in the desired multi
threaded fashion.
Is it
How exactly do you spawn request handlers? Do you call a reentrant
handler VI dynamically with the run method?
It's possible to have multiple connection handlers that handle
requests in parallell, I do that in several of my client-server
applications. All clients connect to the same port, that's
