volse-hubzilla.git - Volse Hubzilla -- soft fork of main Hubzilla core for Volse

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	reddav - basic mkdir support - needs more work to be robust	friendica	2014-01-05	1	-5/+104
\|
*	more dav work	friendica	2014-01-03	1	-8/+71
\|
*	basic browsing and file retrieval for webdav working - uploads not yet. A ↵	friendica	2014-01-02	1	-59/+126
\| \| \| \|	lot of permissions stuff is in place so it's marginally (but probably not completely) permission controlled
*	some DAV tweaks before the next round of heavy lifting	friendica	2014-01-02	1	-67/+193
\|
*	return to working on red-dav; This is a bit of a slog at the moment and the ↵	friendica	2014-01-01	1	-14/+102
\| \| \| \|	basic framework isn't even close to working. This does break the working test we did have (which was never connected to the Red backend). Now we're starting to connect Red and DAV together intimately. There will probably be some twists and turns along the way as we get the information we need into all the class objects that need them. But the important part is that the RedDirectory and RedFile classes are loading without throwing white screens and from here we can use logging to figure out what the DAV front end is trying to do and what it is passing to the backend and hopefully figure out what it expects to do with the results. Unless you're a competent developer with a strong background in OOP and are helping develop this code, you should keep it an arm's length away from any production site and don't even think of enabling it. By default it is turned off.
*	doco	friendica	2013-10-28	1	-0/+18
\|
*	a bit more progress on DAV driver	friendica	2013-10-27	1	-3/+27
\|
*	include/reddav.php is the glue between Red attachments and the SabreDav ↵	friendica	2013-10-26	1	-0/+154
	interfaces. Much work remains beofre we're ready to actually use this interface. Think of it as a conceptual outline and I'm starting to fill it in from the top down.