Binary file storage locations

Previous topic

Setup & design

Next topic

Author	Message
James Robertson	Wednesday 17 May 2006 3:06:43 pm What is the difference between the various locations in which binary files are stored (in the filesystem)? For example: design/standard/templates/content/datatype/view/ezbinaryfile.tpl uses an ugly looking concat() statement to build a file path like this: http://example.com/content/download/2763/31387/version/3/file/ENUtxt.pdf whereas design/standard/templates/content/datatype/view/ezbinaryfile_direct.tpl uses $attribute.content.filepath property, which contains a filepath like this: http://example.com/var/biotech/storage/original/application/427211c95c56412fe1da1671af5f40fc.pdf What's the difference (apart from the fact that the second example is clearer to achieve but look uglier)? Also, Is the second example version controlled (ie. will $attribute.content.filepath always point to the latest version of the file)? Why are the files (apparently) stored twice?
Bruce Morrison	Wednesday 17 May 2006 4:35:37 pm Hi James The first example is a passthrough and will utilise eZ access checking etc, ensuring that the user accesing the file has the correct permissions to view the file (based on access to the parent object). The second example will be a direct link to the file. The file is stored once. Cheers Bruce My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
James Robertson	Thursday 18 May 2006 3:17:22 pm Thanks Bruce. [Looking at this again, I should have been able to work this out myself. Must have been a bad day ;-] Wouldn't it be nice to have the 'passthrough' URL available as a property of the binary_file attribute, just like the filepath (ie. 'direct link'), instead of having to create it using that horrible concat() statment (with all those naughty hard-coded partial path names). Were do I apply to make this happen?

Author

Message

James Robertson

Wednesday 17 May 2006 3:06:43 pm

What is the difference between the various locations in which binary files are stored (in the filesystem)?

For example:
design/standard/templates/content/datatype/view/ezbinaryfile.tpl
uses an ugly looking concat() statement to build a file path like this:
http://example.com/content/download/2763/31387/version/3/file/ENUtxt.pdf

whereas
design/standard/templates/content/datatype/view/ezbinaryfile_direct.tpl
uses $attribute.content.filepath property, which contains a filepath like this:
http://example.com/var/biotech/storage/original/application/427211c95c56412fe1da1671af5f40fc.pdf

What's the difference (apart from the fact that the second example is clearer to achieve but look uglier)?

Also, Is the second example version controlled (ie. will $attribute.content.filepath always point to the latest version of the file)?

Why are the files (apparently) stored twice?

Bruce Morrison

Wednesday 17 May 2006 4:35:37 pm

Hi James

The first example is a passthrough and will utilise eZ access checking etc, ensuring that the user accesing the file has the correct permissions to view the file (based on access to the parent object).

The second example will be a direct link to the file.

The file is stored once.

Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

James Robertson

Thursday 18 May 2006 3:17:22 pm

Thanks Bruce. [Looking at this again, I should have been able to work this out myself. Must have been a bad day ;-]

Wouldn't it be nice to have the 'passthrough' URL available as a property of the binary_file attribute, just like the filepath (ie. 'direct link'), instead of having to create it using that horrible concat() statment (with all those naughty hard-coded partial path names). Were do I apply to make this happen?

eZ debug

Timing:	Jan 19 2025 00:08:22
Script start
Timing:	Jan 19 2025 00:08:22
Module start 'layout'
Timing:	Jan 19 2025 00:08:22
Module start 'content'
Timing:	Jan 19 2025 00:08:23
Module end 'content'
Timing:	Jan 19 2025 00:08:23
Script end

Main resources:

Total runtime	1.6193 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	587.9141	152.6250
Module start 'layout'	0.0064	0.0035	740.5391	39.4453
Module start 'content'	0.0099	1.6081	779.9844	541.3203
Module end 'content'	1.6180	0.0013	1,321.3047	12.4766
Script end	1.6193		1,333.7813

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.2109	16	0.0002
Check MTime	0.0014	0.0837	16	0.0001
Mysql Total
Database connection	0.0014	0.0871	1	0.0014
Mysqli_queries	1.5616	96.4361	57	0.0274
Looping result	0.0006	0.0399	55	0.0000
Template Total	1.5803	97.6	2	0.7902
Template load	0.0021	0.1272	2	0.0010
Template processing	1.5783	97.4652	2	0.7891
Template load and register function	0.0001	0.0091	1	0.0001
states
state_id_array	0.0017	0.1042	1	0.0017
state_identifier_array	0.0016	0.1011	2	0.0008
Override
Cache load	0.0017	0.1041	28	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0432	2	0.0003
Fetch class attribute name	0.0017	0.1029	5	0.0003
XML
Image XML parsing	0.0023	0.1397	2	0.0011
class_abstraction
Instantiating content class attribute	0.0000	0.0008	6	0.0000
General
dbfile	0.0031	0.1913	22	0.0001
String conversion	0.0000	0.0004	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
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 17 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs