Tweeted twitter.com/#!/StackTridion/status/589443699790184448
2 added 4 characters in body
source | link

For the first time ever, I am using the SSHFTP transport mechanism due to some infrastructure restrictions. On the whole it works very well, and seems much faster and more stable than HTTP publishing. Unfortunately our editors often publish really large PublishTransactions (like 800Mb or bigger). This often hangs up the Transport and Deployer Services.

In the past, this was less of a problem, as the HTTPUpload Application had a max upload size limit of 100Mb. This meant that those actions failed, but the users knew that meant they had to publish smaller packages.

I am looking for a way to make the publish action fail before the file is sent to the Deployer server via SSHFTP. Is there any out of the box mechanism for this? My only current thought is to us the TransportPackageHandler (can I access the size of the package there?). Is that supported yet with 2013 SP1?Is that supported yet with 2013 SP1?

For the first time ever, I am using the SSHFTP transport mechanism due to some infrastructure restrictions. On the whole it works very well, and seems much faster and more stable than HTTP publishing. Unfortunately our editors often publish really large PublishTransactions (like 800Mb or bigger). This often hangs up the Transport and Deployer Services.

In the past, this was less of a problem, as the HTTPUpload Application had a max upload size limit of 100Mb. This meant that those actions failed, but the users knew that meant they had to publish smaller packages.

I am looking for a way to make the publish action fail before the file is sent to the Deployer server via SSHFTP. Is there any out of the box mechanism for this? My only current thought is to us the TransportPackageHandler (can I access the size of the package there?). Is that supported yet with 2013 SP1?

For the first time ever, I am using the SSHFTP transport mechanism due to some infrastructure restrictions. On the whole it works very well, and seems much faster and more stable than HTTP publishing. Unfortunately our editors often publish really large PublishTransactions (like 800Mb or bigger). This often hangs up the Transport and Deployer Services.

In the past, this was less of a problem, as the HTTPUpload Application had a max upload size limit of 100Mb. This meant that those actions failed, but the users knew that meant they had to publish smaller packages.

I am looking for a way to make the publish action fail before the file is sent to the Deployer server via SSHFTP. Is there any out of the box mechanism for this? My only current thought is to us the TransportPackageHandler (can I access the size of the package there?). Is that supported yet with 2013 SP1?

1
source | link

Limiting transport file size when using SSHFTP transport

For the first time ever, I am using the SSHFTP transport mechanism due to some infrastructure restrictions. On the whole it works very well, and seems much faster and more stable than HTTP publishing. Unfortunately our editors often publish really large PublishTransactions (like 800Mb or bigger). This often hangs up the Transport and Deployer Services.

In the past, this was less of a problem, as the HTTPUpload Application had a max upload size limit of 100Mb. This meant that those actions failed, but the users knew that meant they had to publish smaller packages.

I am looking for a way to make the publish action fail before the file is sent to the Deployer server via SSHFTP. Is there any out of the box mechanism for this? My only current thought is to us the TransportPackageHandler (can I access the size of the package there?). Is that supported yet with 2013 SP1?