#1 AFP stack functional issues

In attempting to do some testing of my own AFP client stack against Jaffer, I've discovered several functional issues with the code:

- When doing DSIOpenSession (to start the AFP session), if I don't supply a parameter (like, say, an attention quantum of 2) to the request, Jaffer fails horribly. Apple's AFP server (both in OS 9 and OS X) does not require this, nor does netatalk.
- Both the FPGetForkParms and FPSetForkParms calls seem to be pretty broken. I cannot get any parameters (like file ID, parent directory ID or file name) via FPGetForkParms, and attempting to use FPSetForkParms to set the fork lengths does nothing.

This was all the further I was able to get using 'fsx' to beat on the mounted export, which goes over 2 million operations with no failures when connected to an OS X AFP server.

[Anonymous]

Also, it seems there is no support for either UTF-8 path names, or UNIX permissions.

[Anonymous]

Also, no NetworkAddresses are provided in the DSIGetStatus call response. I see this is a TODO in the source, but these are serious deficiencies for an AFP server that claims to implement AFP 3.x.