Al Byers wrote: > Can someone explain how this approach compares to what WebSlinger brings?
Webslinger is a filesystem content repository. As much as possible, everything is stored in a normal, plain, simple filesystem. I can't emphasize this enough. FILESYSTEM. Please, everything filesystem. Files, directories, everything on disk. The reasons for this, are so *normal* editors(vim/eclipse/dreamweaver/photoshop) can deal with the content, normal revision control systems(svn/git/whatever) can deal with it, samba/nfs sharing works, scp/rsync work. There is just too much useful stuff that can be done with regular files, so why reinvent the wheel, by storing in some other location?
