afp:// vs. smb://

I managed to get Appletalk (well, technically, Localtalk) working on my FreeBSD-based fileserver, but I still haven’t managed to work out the permissions, on the Linux webserver (running clarkconnect). So I’m “regularly” mounting both afp shares (music and software archives – I keep the iPhoto pics on the local drive) and smb shares (the sites dir), and have noticed some things.

AFP is much more tolerant of interruptions or transitions in network service. Both when resuming from sleep and the switch from Airport to Ethernet (or vice versa), the afp shares stay alive. The smb share, however, never fails to, well, fail. And then, boom, up comes the “The server you were connected to is no longer available…” message. Much nicer.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s