discuss-gnustep
[Top][All Lists]
Advanced

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

Re: DO P2P?


From: Richard Frith-Macdonald
Subject: Re: DO P2P?
Date: Tue, 26 Mar 2002 19:04:05 +0000

On Tuesday, March 26, 2002, at 06:22 PM, Stephen G.Walizer wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm thinking about doing an app that needs limited P2P functionality (number
of clients should be small, probably never more than 100, as opposed to
something that's designed to scale to a huge number of users) and I had some
questions about ObjC DO and its suitability to this.

I'm still learning ObjC and the APIs so please pardon any dumb questions =)

I've read Nicola Pero's DO tutorial, but I'm looking for something more in depth. The tutorial covers a single server (or 2, one local one remote). Is
it possbile to have an arbitrary number of servers providing the same
functionality and call then all?

Yes.

Is there a way to find all servers for a
service on a network?

Apart from polling all the hosts, no. Though you can ask for a server without
specifying any particular host, and you will get one chosen arbitrarily.

Anybody know of any in-depth docs on this?

No ... though there is some stuff in the programming manual in GNUstep-base

Also, is there a way to implement security in the actual network calls?
SSL for transmissions and identifying clients and only allowing certain
clients to perform certain actions?


Yes/no. An NSConnection delegate can provide authorisation data for each call,
which is intended to let you do things like provide a message digest.
In GNUstep the API is slightly extended ... the delegate may not only add/verify authorisation data, it may replace the data objects being sent with encrypted
copies.

I know GNUStep DO can't interoperate with OS X DO, but are there any gotchas at the API level I should be aware of, as I would want the application to be source compatible on both. It seems to me I read about a makefile setting that would restrict usage to OS X compatibility, but I can't find it now =)

In that case, you can't easily get encryption ... the MacOS-X API won't allow
that (afaik) without re-implementing significant chunks of the code
eg. re-implementing NSPortCoder
If you are happy to just use authorisation to ensure that the data is not
tampered with, the standard API will do for you.





reply via email to

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