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