On Thu, 29 Jul 1999, Frederick Bruckman wrote:

> On Thu, 29 Jul 1999, Ken Nakata wrote:
> > You mean, hfsfs exports the resource forks in either netatalk way or
> > CAP way?

Yes. ;-)

> To change the subject, one thing that annoys me about netatalk is that
> it creates an .AppleDouble/file for every single file, whether it has
> or had a resource fork or not. Does CAP not do that? What is CAP
> anyway? Is that the AppleServer?

The AppleDouble file also contains the finder info, which CAP stores in a
third file.

CAP is the Columbia Appletalk Package. It was developed in the mid to late
eighties, and was a direct implimentation of the Appletalk libraries in C.
Thus it's a very Pascal'y thing. It relies on various filtering mechanisms
for a userland daemon to route packets. It's all in userland.

Netatalk impliments Appletalk in the kernel just like any other protocol.
It's much faster.

Take care,

Bill