How Different Versions Managed in WEBDAV

Next topic

Author	Message
John Smith	Tuesday 17 October 2006 10:14:31 am Hi There, Hope some body can help. I just went through version mechanism. Very nice piece of mechanism when two users working on same article or document. I just want to know how ezpublish will deal with version mechanism when somebody is uploading/editing all the stuff via WEBDAV. Does version mechanism comes into play when you are browsing, creating, removing, uploadin, downloadin, renaming etc. files and directories on a web server using WEBDAV. cheers Smith....
Björn Dieding@xrow.de	Friday 27 October 2006 12:08:27 pm The answer is yes Webdav also has versioning control. Though you only see the latest version(published) in your explorer. Also once you delete with webdav the object is deleted with out trash. Meaning you loose all. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
John Smith	Saturday 28 October 2006 1:23:12 am Thanks Björn, for your kind reply. What is the best apache version you recommend for Webdav support. Somebody told me lastest apache 2.0.x is best for webdav. It handles locking and other few things better than apache 1.3..x Cheers Smith
Paul Borgermans	Saturday 28 October 2006 8:06:26 am The version of Apache does not matter for webdav in ez publish as it uses its own implementation hth Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

eZ debug

Timing:	Jan 19 2025 11:53:54
Script start
Timing:	Jan 19 2025 11:53:54
Module start 'layout'
Timing:	Jan 19 2025 11:53:54
Module start 'content'
Timing:	Jan 19 2025 11:53:54
Module end 'content'
Timing:	Jan 19 2025 11:53:54
Script end

Main resources:

Total runtime	0.7630 sec
Peak memory usage	4,096.0000 KB
Database Queries	62

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0049	589.2813	152.6406
Module start 'layout'	0.0049	0.0032	741.9219	39.4609
Module start 'content'	0.0080	0.7536	781.3828	586.2813
Module end 'content'	0.7617	0.0013	1,367.6641	12.1406
Script end	0.7630		1,379.8047

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4553	16	0.0002
Check MTime	0.0013	0.1713	16	0.0001
Mysql Total
Database connection	0.0006	0.0767	1	0.0006
Mysqli_queries	0.7063	92.5730	62	0.0114
Looping result	0.0006	0.0839	60	0.0000
Template Total	0.7240	94.9	2	0.3620
Template load	0.0026	0.3345	2	0.0013
Template processing	0.7215	94.5584	2	0.3607
Template load and register function	0.0002	0.0262	1	0.0002
states
state_id_array	0.0021	0.2813	1	0.0021
state_identifier_array	0.0021	0.2790	2	0.0011
Override
Cache load	0.0021	0.2769	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0934	3	0.0002
Fetch class attribute name	0.0014	0.1831	6	0.0002
XML
Image XML parsing	0.0044	0.5732	3	0.0015
class_abstraction
Instantiating content class attribute	0.0000	0.0017	6	0.0000
General
dbfile	0.0053	0.6941	23	0.0002
String conversion	0.0000	0.0007	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 12 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs