4

I'm trying to do the following with a modified version of the echo server example that comes with the cocoaasyncsocket library:

1) open a connection to a python script acting as a server
2) send data // works, but delegate doesn't fire
3) receive data back // delegate doesn't fire
4) disconnect // doesn't disconnect, apparently still in my thread

Currently I open a connection in the didFinishLaunchingWithOptions delegate, and then attempt to send data in the didConnectToHost delegate. I then attempt to read data coming back from the client and then disconnect.

I am able to open a connection and send data (which the server verifies as received) but the didWriteDataWithTag delegate never fires. However, the server receive the data. The server then fires back some data, but the didReadData doesn't fire either.

Beside the fact the read/write delegates aren't firing, it seems the way I'm organizing my code is not right, but I'm not sure how this looks in an event-driven system as opposed to run loop (I'm a novice at event-driven stuff + networking). If I have a series of actions whose respective completions are triggered by their delegates, should the delegates be sharing some sort of messages- ie we recieved an "xxx" message, write back "yyy"? I'd prefer to have one function which manages all of this. Is there a canonical way of doing this?

IPhoneConnectTestAppDelegate.m (snippets)

- (void)localConnect {
    NSError *error = nil;
    if (![asyncSocket connectToHost:@"localhost" onPort:5000 error:&error]) {
        DDLogError(@"Error connecting: %@", error);
    }
}

- (void)disconnect {
    [asyncSocket setDelegate:nil];
    [asyncSocket disconnect];
    [asyncSocket release];
}

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    // Setup our socket (GCDAsyncSocket).
    dispatch_queue_t mainQueue = dispatch_get_main_queue();
    asyncSocket = [[GCDAsyncSocket alloc] initWithDelegate:self delegateQueue:mainQueue];

    [self localConnect];

    // Add the view controller's view to the window and display.
    [window addSubview:viewController.view];
    [window makeKeyAndVisible];
}


- (void)onSocket:(GCDAsyncSocket *)sock didReadData:(NSData *)data withTag:(long)tag {
    NSString *output = [[NSString alloc] initWithData:data encoding:NSASCIIStringEncoding];
    NSLog(@"didReadData: %@", output);

}

- (void)onSocket:(GCDAsyncSocket *)sock didWriteDataWithTag:(long)tag {
    NSLog(@"didWriteDataWithTag");
}

- (void)socket:(GCDAsyncSocket *)sock didConnectToHost:(NSString *)host port:(UInt16)port {
    NSLog(@"socket:%p didConnectToHost:%@ port:%hu", sock, host, port);
    if(port == 5000)
    {
        NSString *msg = @"q";
        NSData *dataOut = [msg dataUsingEncoding:NSASCIIStringEncoding];
        [asyncSocket writeData:dataOut withTimeout:-1 tag:0];
        [asyncSocket readDataWithTimeout:-1 tag:0];
        [self disconnect];
    }
}

tcpserver.py

# TCP server example
import socket, time
server_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
server_socket.bind(("", 5000))
server_socket.listen(5)

print "TCPServer Waiting for client on port 5000"

while 1:
    client_socket, address = server_socket.accept()
    print "I got a connection from ", address
    while 1:
        data = client_socket.recv(512)
        print "Data from client",data

        time.sleep(2)
        data = "xxx"
        print "Sending data to client",data
        client_socket.send (data)
        break;
Deepak Danduprolu
  • 44,595
  • 12
  • 101
  • 105
nflacco
  • 4,972
  • 8
  • 45
  • 78
  • For what it's worth I had far less trouble with the Simple Socket wrapper around BSD sockets and putting those operations on a worker thread. – nflacco May 16 '12 at 17:05

3 Answers3

7

I know this is an old question with an already accepted answer, but to clarify for people who find this thread looking for something, the reason the delegate methods didn't get called is because the GCDAsynchSocket start with socket: instead of onsocket: ie:

- (void)onSocket:(AsyncSocket *)sock didWriteDataWithTag:(long)tag

becomes:

- (void) socket:(GCDAsyncSocket *)sock didWriteDataWithTag:(long)tag
Mike Wallace
  • 276
  • 2
  • 7
4

A friend of a friend figured it out for me! We were not able to get GCDAsyncSocket to work properly (connect and write, but not read). AsyncSocket however functions in all 3 respects, and all the delegates work properly.

#import "AsyncSocket.h"
#import "tcp_clientViewController.h"

@implementation tcp_clientViewController

@synthesize socket;



-(IBAction)connect:(id)sender { 
    NSLog(@"(IBAction)connect");
    NSError *error = nil;
    if (![socket connectToHost:@"localhost" onPort:5000 error:&error]){
        NSLog(@"Error connecting: %@", error);
    }
}

-(IBAction)send:(id)sender {
    NSLog(@"(IBAction)send");


    char bytes[] = "abcd\r\n";
    NSData* data = [[NSData alloc] initWithBytes:bytes length:sizeof(bytes)];

    //NSString *msg = @"xxxxx\r\n";
    //NSData *data = [msg dataUsingEncoding:NSUTF8StringEncoding];


    [socket writeData:data withTimeout:-1 tag:0];
    //NSData *data = [asyncSocket readDataWithTimeout:-1 tag:0];
    [data release];

    [socket readDataToData:[AsyncSocket LFData] withTimeout:-1 tag:0];
}

- (void)viewDidLoad {
    // initialize socket
    socket = [[AsyncSocket alloc] initWithDelegate:self];
}

#pragma mark AsyncSocket Delegate Methods
-(void)onSocket:(AsyncSocket *)sock didWriteDataWithTag:(long)tag {
    NSLog(@"socket:%p didWriteDataWithTag:%@", sock, tag);
}

- (void)socket:(AsyncSocket *)sock didWritePartialDataOfLength:(NSUInteger)partialLength tag:(long)tag {
    NSLog(@"socket:%p didWritePartialDataOfLength:%@ tag:%@", sock, partialLength, tag);
}

- (void)onSocket:(AsyncSocket *)sock didConnectToHost:(NSString *)host port:(UInt16)port
{
    NSLog(@"socket:%p didConnectToHost:%@ port:%hu", sock, host, port);
}

- (void)socketDidSecure:(AsyncSocket *)sock
{
    NSLog(@"socket:%p socketDidSecure", sock);
}

- (void)socketDidDisconnect:(AsyncSocket *)sock withError:(NSError *)err
{
    NSLog(@"socket:%p socketDidDisconnect withError: %@", sock, err);
}

- (void)onSocket:(AsyncSocket *)sock didReadData:(NSData *)data withTag:(long)tag
{
    NSString* newStr = [NSString stringWithUTF8String:[data bytes]];    
    NSLog(@"socket socketDidReadData:%@", newStr);
}

-(IBAction)disconnect:(id)sender { }

#pragma mark View stuff
- (void)didReceiveMemoryWarning {
    [super didReceiveMemoryWarning];
}

- (void)viewDidUnload {}

- (void)dealloc {
    self.socket = nil;
    [super dealloc];
}

@end
nflacco
  • 4,972
  • 8
  • 45
  • 78
2

Try to use local sock for reading commands and to put them in the write command

- (void)onSocket:(AsyncSocket *)sock didWriteDataWithTag:(long)tag
{
    [sock readDataToData:[AsyncSocket LFData] withTimeout:-1 tag:tag];
}
albianto
  • 4,092
  • 2
  • 36
  • 54
  • Hmm I tried `[asyncSocket readDataToData:[GCDAsyncSocket CRLFData] withTimeout:-1 tag:0];` (and LFData) and send from the python server the `client_socket.send("xxx\r\n")` and the delegate doesn't fire. The write delegate doesn't fire either, but the data gets sent.... hmmmm – nflacco Jun 18 '11 at 02:18
  • If the write delegate doesn't fire, make sure you're setting it properly – albianto Jun 18 '11 at 08:25
  • Doesn't the initialization of the socket `asyncSocket = [[GCDAsyncSocket alloc] initWithDelegate:self delegateQueue:mainQueue];` set the delegates up properly? The didConnectToHost delegate fires, so doesn't the mean the other asyncsocket delegates should be set too? I'm very new to cocoa programming so this is all a bit new to me. I looked at [a SOF question on delegates](http://stackoverflow.com/questions/626898/how-do-i-create-delegates-in-objective-c) but it didn't clarify things. – nflacco Jun 18 '11 at 22:21
  • AsyncSocket was really difficult to set up for me – albianto Jun 19 '11 at 04:47
  • I tried that- did not work. Right now I'm focusing on getting the write delegate to fire; I know the data gets sent because the server sees it! I tried two different approaches today. First I changed the length of data received by the server from 512 to 4 per socket communication, and made a 5 byte message from the client. I thought perhaps the server was waiting for a complete communication before confirming the data was sent. Didn't work- message sent and received, but no delegate firing. I then modified the CocoaForScientists example with a message broker class, but that didn't work either! – nflacco Jun 20 '11 at 05:30
  • It could be many things, the only way for you is to try to debug and to find a solution yourself. I've worked 2 weeks before getting my AsyncSocket project working. – albianto Jun 20 '11 at 09:44