Hi All,
I am pretty new to GNUStep but I think I will use it for my upcoming
project. It is a multilayer online game for iPhone. Initially I though
to program the server in C++. The client is clear - a native Objective C
application. Currently I am looking for a good solution for the
Let me just put you out of your future misery now: it's impossible.
The communication protocol is so fucking different that Apple
server-GNUstep client/GNUstep server-Apple communication client is
like Fox News praising Obama's every move. You'ld have to use GNUstep
or Apple for both ends.
I'm not sure why this follows. Just because you can't use DO doesn't
mean you can't use GNUstep on the server.
By the way, in theory it ought to be possible to port GNUstep's
NSPortCoder to Cocoa and use this for serialising messages to be sent
across sockets. This would let Cocoa apps
On Tue, Aug 25, 2009 at 4:49 PM, David Chisnallthera...@sucs.org wrote:
I'm not sure why this follows. Just because you can't use DO doesn't mean
you can't use GNUstep on the server.
By the way, in theory it ought to be possible to port GNUstep's NSPortCoder
to Cocoa and use this for
Hi All,
On 25 Aug 2009, at 16:49, David Chisnall wrote:
By the way, in theory it ought to be possible to port GNUstep's
NSPortCoder to Cocoa and use this for serialising messages to be
sent across sockets. This would let Cocoa apps talk to GNUstep ones
via DO.
This may be a useful
Good point David,
Actually, the server application will mainly deal with networking, in
memory data structures manipulations, threads and database interactions.
If I use GNUStep to develop it, I will be later on able to reuse all
data models and networking modules directly for the iPhone
The issue is that DO on the Mac uses the older typed-stream data
format. This was something we were never inclined to reverse
engineer.
GC
On Tue, Aug 25, 2009 at 11:49 AM, David Chisnallthera...@sucs.org wrote:
I'm not sure why this follows. Just because you can't use DO doesn't mean
you
Hi,
Note that writing a plist reader in java or C++ is quite simple.
Another possibility is to use XML-RPC, which has implementation
everywhere. But this is quite verbose (even if it's far from the
abomination that SOAP is).
I think sending over plists sounds good.
I add to the discussion
Gregory Casamento wrote:
The issue is that DO on the Mac uses the older typed-stream data
format. This was something we were never inclined to reverse
engineer.
GC
Yes, that is the main problem, the rest would work. I think somebody
worked in that direction. I think it was Nikolaus and
On 25 Aug 2009, at 17:17, Nicolas Roard wrote:
On Tue, Aug 25, 2009 at 4:49 PM, David Chisnallthera...@sucs.org
wrote:
I'm not sure why this follows. Just because you can't use DO
doesn't mean
you can't use GNUstep on the server.
By the way, in theory it ought to be possible to port
Hi,
In my experience, the simplest (one-liner!) and robustest solution was
indeed to send plist-serialised data over the wire -- both platforms
(GNUstep and OSX) support fast serialization/deserialisation to plist,
and as an added benefit this is easier to debug as the data is sent in
clear,
Nice spot Michael!
It is really nice that during development I could extend the messages
(protocol) without forcing the old version running client applications
first to update and then allow then to connect to the server.
Having compiled reader and writer is much better for me than
On Tue, Aug 25, 2009 at 9:45 PM, Michael
Thalermichael.tha...@physik.tu-muenchen.de wrote:
Hi,
In my experience, the simplest (one-liner!) and robustest solution was
indeed to send plist-serialised data over the wire -- both platforms
(GNUstep and OSX) support fast
13 matches
Mail list logo
