FROM : William Zumwalt
DATE : Sat Jan 05 02:49:34 2008
I'm developing on 10.4 and have already implemented my thread using mach
ports as your first link shows, this is how my client sends the msgs to my
server thread.
However, my client is blocking when the msgs are sent to the server unless I
use the protocol modifiers (like oneway) on the thread, which then give me a
different problem.
On Jan 4, 2008 7:38 PM, <marcelo.<email_removed>> wrote:
> >
> > However my problem now is that with all three marked as (oneway void)
> > (sending async msgs), message #2 requires a few seconds to complete
> > while
> > message #3 depends on message #2 before it can start, yet msg #3 is
> > done
> > before msg #2 can finish. I've also seen once where they arrived out
> > of
> > order.
> >
> >
> > // from the client
> >
> > [server sendMsg1];
> >
> > [server sendMsg2];
> >
> > [server sendMsg3];
> >
> >
> > Is there another way to call asynchronously, yet guarantee that the
> > messages
> > arrive in order? Or someway to call w/o the GUI blocking for a server
> > message return?
>
>
> You can use :
> - NSConnection/NSPorts (
> http://developer.apple.com/documentation/Cocoa/Conceptual/Multithreading/articles/SocketComm.html#/
> /apple_ref/doc/uid/TP40001479 )
> - YAMessageQueue (10.4-): http://www.2pi.dk/tech/cocoa/message_queue.html
> - NSOperation/NSOperationQueue (10.5+) :
> - [NSObject performSelector:onThread]/[NSObject
> performSelectorInMainThread:] (10.5+);
>
>
> :: marcelo.alves
>
DATE : Sat Jan 05 02:49:34 2008
I'm developing on 10.4 and have already implemented my thread using mach
ports as your first link shows, this is how my client sends the msgs to my
server thread.
However, my client is blocking when the msgs are sent to the server unless I
use the protocol modifiers (like oneway) on the thread, which then give me a
different problem.
On Jan 4, 2008 7:38 PM, <marcelo.<email_removed>> wrote:
> >
> > However my problem now is that with all three marked as (oneway void)
> > (sending async msgs), message #2 requires a few seconds to complete
> > while
> > message #3 depends on message #2 before it can start, yet msg #3 is
> > done
> > before msg #2 can finish. I've also seen once where they arrived out
> > of
> > order.
> >
> >
> > // from the client
> >
> > [server sendMsg1];
> >
> > [server sendMsg2];
> >
> > [server sendMsg3];
> >
> >
> > Is there another way to call asynchronously, yet guarantee that the
> > messages
> > arrive in order? Or someway to call w/o the GUI blocking for a server
> > message return?
>
>
> You can use :
> - NSConnection/NSPorts (
> http://developer.apple.com/documentation/Cocoa/Conceptual/Multithreading/articles/SocketComm.html#/
> /apple_ref/doc/uid/TP40001479 )
> - YAMessageQueue (10.4-): http://www.2pi.dk/tech/cocoa/message_queue.html
> - NSOperation/NSOperationQueue (10.5+) :
> - [NSObject performSelector:onThread]/[NSObject
> performSelectorInMainThread:] (10.5+);
>
>
> :: marcelo.alves
>
| Related mails | Author | Date |
|---|---|---|
| William Zumwalt | Jan 5, 02:06 | |
| marcelo.alves | Jan 5, 02:38 | |
| John Stiles | Jan 5, 02:48 | |
| William Zumwalt | Jan 5, 02:49 | |
| William Zumwalt | Jan 5, 02:54 | |
| Ken Thomases | Jan 5, 08:36 | |
| James Bucanek | Jan 5, 17:09 | |
| William Zumwalt | Jan 5, 22:35 | |
| William Zumwalt | Jan 5, 22:44 | |
| James Bucanek | Jan 6, 02:35 | |
| James Bucanek | Jan 6, 02:35 | |
| William Zumwalt | Jan 6, 03:35 | |
| glenn andreas | Jan 6, 04:16 | |
| William Zumwalt | Jan 6, 04:25 | |
| James Bucanek | Jan 6, 08:04 | |
| William Zumwalt | Jan 6, 09:28 | |
| Steve Weller | Jan 6, 18:55 |






Cocoa mail archive

