Custom handling of audio files in ezfile datatype

Previous topic

Next topic

Author	Message
H-Works Agency	Wednesday 14 November 2007 10:44:12 am Hi all, I use the classic ezfile datatype inside a product class. What technique should i use to use different storage based on file mimetype ? Do i have to create a custom datatype ? Do i have to use the fileHandler ? If yes how does this works ? What is the differences between upload.ini, file.ini and binaryfile.ini ? Thanx for any help or comment. EZP is Great

Author

Message

Wednesday 14 November 2007 10:44:12 am

Hi all,

I use the classic ezfile datatype inside a product class.

What technique should i use to use different storage based on file mimetype ?

Do i have to create a custom datatype ?

Do i have to use the fileHandler ? If yes how does this works ? What is the differences between upload.ini, file.ini and binaryfile.ini ?

Thanx for any help or comment.

EZP is Great

eZ debug

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0076	588.2656	151.2266
Module start 'layout'	0.0076	0.0051	739.4922	220.7344
Module start 'content'	0.0127	0.0129	960.2266	993.7422
Module end 'content'	0.0257	0.0018	1,953.9688	29.9922
Script end	0.0275		1,983.9609

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	10.3184	14	0.0002
Check MTime	0.0011	4.1386	14	0.0001
Mysql Total
Database connection	0.0007	2.6927	1	0.0007
Mysqli_queries	0.0053	19.4056	3	0.0018
Looping result	0.0000	0.0545	1	0.0000
Template Total	0.0014	5.2	1	0.0014
Template load	0.0012	4.2139	1	0.0012
Template processing	0.0003	0.9622	1	0.0003
Override
Cache load	0.0007	2.3631	1	0.0007
General
dbfile	0.0003	1.0911	8	0.0000
String conversion	0.0000	0.0398	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0002 secs