Open Transport and MultiProcessing Services
Open Transport and MultiProcessing Services
- Subject: Open Transport and MultiProcessing Services
- From: Igor garnov <email@hidden>
- Date: Tue, 18 May 2004 23:39:22 +0400
Hello
I am experiencing strange bugs in my app. This is Carbon CFM
application intended to run on both OS 9 and X.
During initialization it creates an MP task. In this "secondary" task,
any attempt at sending or receiving data on an endpoint results in
crash unless it is done by means of MPRemoteCall.
But, to my surprise, even when I call OTConnect from my "primary" task,
my app crashes as well. I think my next step will be to try
MPRemoteCall here, too. But even if this approach works out in this
particular case, I am not sure that this is the best practice.
I appreciate the simplicity of code, which is achieved when using Open
Transport with asynchronous notification callbacks. I would like to be
able to utilize OT notifiers as wide as possible in my application when
it comes to networking. Is this possible if I have to use MP tasks as
well? Or are MP tasks just incompatible with asynchronous operation of
OT?
I realize that this all would not be the case if I used an approach
without MP tasks. But it is done this way, and now I can only think of
constructing further code so that it worked with the existing layout.
Can I use Open Transport in synchronous mode in MP tasks?
Regards,
Igor
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.