Hello Ryan,
Please note that the slowdown is alos because of the logging. Writing to
screen is very slow in windows. If you still need the logging then you
have to do it in main thread also eather by synchronizing or by posting
messages with the log data.
About the threading. I think you only need 1 thread to run the whole
thing in. The most easy is to work in 2 step:
- First turn thw whole communication with all his components into a
object. Give it an event for the outputs (logging).
- Then create the object in main form create and run / test it.
- if all runs fine then make it a thread. this give minimal changes and
you can do full testing without a thread.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Monday, May 29, 2006, 01:01, Ryan Saddler wrote:
I am inquiring about the socket spy program and how difficult it would be to
thread it? I examined thrdsrv1 example in ics examles and want to know where
to begin. If anyone can point me in the right direction please. The current
program works great but threading is required because the traffic is fairly
heavy even for asynchronous sockets so I feel it needs threaded so that my
main gui thread does not slow to a crawl.
Thanks,
Ryan S.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
