HFS 3 will have both web-based (but separated) front-end and back-end.
About the front-end, this is the logic i want to apply:
when you access it, you get a web-app for browsing folders and files, without page reloading.
This is how the server will behave on requests
switch on url resource type
case 'file': serve file
case 'link': redirect
case 'folder':
switch on $format
case nothing: serve front-end web app, with this folder already selected
case 'tar': serve archive
case 'zip': serve archive
default: error
i planned to use
socket.io for blazing fast communication, and
extjs for the GUI.