I haven't worked through it personally. In my research of WebDAV, I
noticed that some shops were using SVN on WebDAV, and that authoring
tools like Dreamweaver use WebDAV. So, it seemed logical to me to put a
WebDAV interface on the content component.
Let's say you wanted to use the content component as the backing store
for a VCS. Then it would be possible to have a setting in the content
component that would specify something like "Publish repository X,
revision Y at URL Z." The content component could serve the website
right from the repository.
I don't know if it's a good idea or not, but from my perspective it
would be pretty cool.
-Adrian
Ean Schuessler wrote:
Adrian Crum wrote:
Again, that can be handled with WebDAV. GIT can store its repository
on a WebDAV server. A WebDAV interface to the content component could
be designed.
I'm not sure you are working through what would happen there. Would the
.git directory also be stored in WebDAV? The number and complexity of
Content objects that would create would be interesting. I would also be
concerned about the performance.
