[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #36684] GSSocketStream scheduleInRunLoop:forMode: does not

From: Thomas Davie
Subject: [bug #36684] GSSocketStream scheduleInRunLoop:forMode: does not
Date: Tue, 19 Jun 2012 12:25:08 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/534.57.2 (KHTML, like Gecko) Version/5.1.7 Safari/534.57.2


                 Summary: GSSocketStream scheduleInRunLoop:forMode: does not
                 Project: GNUstep
            Submitted by: beelsebob
            Submitted on: Tue 19 Jun 2012 12:25:08 PM GMT
                Category: Base/Foundation
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any



Scheduling socket streams in the run loop does not work correctly.

Steps to reproduce:
1) create a stream pair using getStreamsToHost:port:inputStream:outputStream:
2) Setup delegates correctly, make sure that the streams are retained
3) call -scheduleInRunLoop:[NSRunLoop currentRunLoop]
forMode:NSDefaultRunLoopMode on the two streams.
4) open the streams.

Expected results:
- stream:handleEvent: is called on the delegate for the various interesting
and exciting events that happen.

Actual results:
No messages are sent to the delegate.

1) If -open is called before scheduling the streams in the run loop, an
NSStreamEventOpenCompleted event is sent to the delegate.  No further messages
2) If the private method -addStream:mode: is used instead, all stream events
are forwarded correctly.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]