I run a small web hosting company, and I would like to offer DAV access for all of my users.
I know yaws supports DAV, but the trick is that I want the files uploaded for a particular
user to belong to that user, and not to the "nobody" user.
So... I think what I want is a separate yaws process for each user. But I do not want
these child processes to be running all the time. Instead, I would like them to be created
on the fly and then killed off after a few minutes of inactivity.
I suspect this is going to require some erlang-hacking on my end, but I'm really not sure
where to start. So I was hoping you guys could point me in the right direction. :)
First, does this sound like a reasonable solution. If so, how much work would something
like this be to implement?
I've seen erlang's open_port function, and I thought it might be usable for talking to the
child processes. But would that work well with yaws, or would it be better to do the
communication as an HTTP proxy, with each yaws server running on its own port?
Any help with this would be appreciated.