alternative Download Server

Next topic

Author	Message
Andreas Gellhaus	Thursday 09 October 2003 7:01:41 am Hello, I have a little problem and don't now how to start. When want to use two different servers for our download. Our second download location should be the ezpublish server. So, what should I do??? generate an new binary datatype to upload a file to my ezpublish server and copy it to the special download Server or is it possible to do this by workflows. Who has a good idea, where to start? Thank’s Andreas
Jan Borsodi	Thursday 16 October 2003 1:33:02 am I wouldn't recommend creating a new datatype, to do so you would have to either copy the existing one or create one from scratch. Either way you wouldn't get updates to the file datatype that we make. Creating a workflow is a good way to handle this, create a new custom workflow event that will check the published object, if any of the attribute is a file datatype get the file and send it to your other server. A third way is to fix the file datatype to let the binaryfilehandler to the upload work. Currently the binaryfilehandlers only do the download work, not upload. If this is fixed then you could create your own upload handler. Your handler should call the normal upload handler to store the file locally then send the file to the other server. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Thursday 09 October 2003 7:01:41 am

Hello,

I have a little problem and don't now how to start. When want to use two different servers for our download. Our second download location should be the ezpublish server. So, what should I do??? generate an new binary datatype to upload a file to my ezpublish server and copy it to the special download Server or is it possible to do this by workflows.

Who has a good idea, where to start?

Thank’s
Andreas

Jan Borsodi

Thursday 16 October 2003 1:33:02 am

I wouldn't recommend creating a new datatype, to do so you would have to either copy the existing one or create one from scratch. Either way you wouldn't get updates to the file datatype that we make.

Creating a workflow is a good way to handle this, create a new custom workflow event that will check the published object, if any of the attribute is a file datatype get the file and send it to your other server.

A third way is to fix the file datatype to let the binaryfilehandler to the upload work. Currently the binaryfilehandlers only do the download work, not upload.
If this is fixed then you could create your own upload handler. Your handler should call the normal upload handler to store the file locally then send the file to the other server.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 18 2025 22:12:44
Script start
Timing:	Jan 18 2025 22:12:44
Module start 'layout'
Timing:	Jan 18 2025 22:12:44
Module start 'content'
Timing:	Jan 18 2025 22:12:45
Module end 'content'
Timing:	Jan 18 2025 22:12:45
Script end

Main resources:

Total runtime	0.8105 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

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.0026	740.5391	39.4453
Module start 'content'	0.0090	0.8003	779.9844	521.9688
Module end 'content'	0.8093	0.0012	1,301.9531	8.1641
Script end	0.8105		1,310.1172

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.3805	16	0.0002
Check MTime	0.0013	0.1603	16	0.0001
Mysql Total
Database connection	0.0008	0.0998	1	0.0008
Mysqli_queries	0.7709	95.1114	54	0.0143
Looping result	0.0004	0.0496	52	0.0000
Template Total	0.7819	96.5	2	0.3909
Template load	0.0021	0.2543	2	0.0010
Template processing	0.7798	96.2063	2	0.3899
Template load and register function	0.0001	0.0123	1	0.0001
states
state_id_array	0.0008	0.1004	1	0.0008
state_identifier_array	0.0008	0.1002	2	0.0004
Override
Cache load	0.0017	0.2050	14	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0675	2	0.0003
Fetch class attribute name	0.0008	0.0985	3	0.0003
XML
Image XML parsing	0.0006	0.0721	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0010	3	0.0000
General
dbfile	0.0008	0.0977	17	0.0000
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
2	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/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	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: 11 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs