Depending on the types of applications and documents that you store, you may or may not have troubles with resource forks disappearing.

Probably the best first step would be to see how Windows 2000's AppleTalk support handles the resource forks.

It may separate the resource information, encode it to binary data then chuck it in a separate hidden file to be seamlessly reintegrated when the remote client requests the file. That would be the best case, in which case your idea will work well.