Re: [ERROR] Unable to get socket name. Why?

[Ma Xiaoming]

Hello Jamie,

I don't have an iMac or a MacBook, so I can only study Objective-C with 
GNUstep on Windows. I downloaded a "Base Programming Manual" pdf file to 
study the fundamental of GNUstep. You could find it at 
http://www.gnustep.org/developers/documentation.html. The first PDF for 
downloading at General Manuals section.

In the 7 chapter of this book, it describes a Client/Server structure. I was 
very exciting about it, because it is seems like a great structure for 
Internet game programming. But unfortunately, even I could compile the 
Server code, but I cannot run it on my machine. When I try to run it, the 
command line told me that unable to get socket name. I was so frustrated 
about it, because until now, I cannot figure out what's going on.

Do you have any good idea on it? Many thanks for your help.

Best regards,

Xiaoming


"Jamie Ramone" <sancombru@gmail.com> 
??????:CA+hS6qjX8LtKf75HfMY7fExpWw3UN4gvEo2WGnNyJTua0ZJvfw@mail.gmail.com...
>I have a question, why are you using that method
> (connectionWithReceivePort: sendPort:) to build the connection and why
> are you using the same port object? The correct way (at least
> according to what I've read from Apple documentation...and example
> code in gnu-base) is to use the method +connectionWithName:. That one
> takes care of creating the port objects and hooking up the
> NSConnection object to the current thread's runloop. Then, you assign
> the object to it with -setRootObject:. Finally, you start up the
> default runloop exactly as you do in that example. The point is,
> unless you REALLY, REALLY, REALLY have to, you can safely ignore the
> lower level details like as the port objects and such. hope that helps
> ;-)
>
>
>
>
> -- 
> Besos, abrazos, confeti y aplausos.
> Jamie Ramone
> "El Vikingo"