All of the download links we issue work pretty much the same in re: being unique to each transaction, only good for the file(s) purchased, only valid for the time period and number of attempts you specify, and cloaking your remote file URL when you are hosting the file yourself rather than uploading it to our server. If you are using our Package Products feature to "bundle" several separate files into one product, then the buyer's thank-you/download page will have one such link for each file. If you are providing separate files that need to be combined, you would need to provide the buyer with a method to accomplish that.



As another alternative, you might consider using our SwiftCD integration, so they would duplicate a disc and mail that to the buyer on-demand whenever an order comes in:

1http://www.e-junkie.com/ej/help.integration.htm#pre1

This would also be much less trouble-prone than expecting buyers to complete a massive download which could take up to an hour or longer to complete -- e.g., check out the download-time estimator here:

2http://www.numion.com/Calculators/Time.html2

We have no method to specify different download servers for different regions.



One other alternative you might consider: embed your video in a Web page, and then use our product-specific Redirection feature to send buyers to their viewing page after payment is completed:

http://www.e-junkie.com/ej/help.redirection.htm

Hm, so if you created three separate products for each video, each product having a different remote file URL pointing to a server in its respective region? I suppose that would work, although ultimately everything goes through our own Web cache to the buyer regardless of where the file originates. This is how our download links work, how we can issue a unique link to each buyer and cloak the remote origin of files not uploaded to our server, and how we enforce your link-expiration settings.

Hm, that level of specific backend detail I'll have to refer to Development for an answer, but in a nutshell, our download links for remotely-hosted files work like this:



The link URL we issue to the buyer looks like http://www.e-junkie.com/[...etc.] When the buyer clicks their link to that URL on our server, our backend looks up what product it goes to, and if a Remote Product File URL had been specified for the product, we stream a copy of the file from your file's static URL, through our Web cache, to the buyer, so insofar as the buyer's end can tell, the file is coming from us.



Once this initial download has completed successfully, we retain our cached copy of that download in our Amazon S3 provisions; for every subsequent download, we first check to see if the original copy at your URL has changed, and if not, we simply serve our cached copy from S3 to the buyer. This eliminates unnecessary transfer-bandwidth surcharges or limits for both you and us, and ensures the quickest and most trouble-free download possible for the recipient.

Does this mean the best thing to do with NEW large files is to download them to yourself through e-junkie first so the customer isn't suffering through this process?



my direct files download (on the same connection) in minutes - whereas the e-junkie link on the same machine/connection takes over an hour.

That would probably be a good idea, and that would also verify that you'd configured the Remote Product File URL correctly and that your download links are working.



After you either upload a file to us or stream the first download of a remotely-hosted file through us, within 15 minutes a copy of the file should be synched up to our Amazon S3 storage, so any downloads after that point should be about as fast as can be expected.



Until we get the file synched to S3, we'd be serving it from our Tucson datacenter, where routing across the Internet may not be ideal to all locations, and the bandwidth available to any download is necessarily limited (so one big download can't hog all our bandwidth and effectively DoS ourselves).

successive downloads does not improve the download speed, so if it is "cached" - it's not helping.

Earlier today, our Lead Developer found and fixed a glitch that was causing slow downloads since the past day or so. Let us know if you're continuing to experience any problems with download performance.

TysonAll of the download links we issue work pretty much the same in re: being unique to each transaction, only good for the file(s) purchased, only valid for the time period and number of attempts you specify, and cloaking your remote file URL when you are hosting the file yourself rather than uploading it to our server.

Hi Tyson



I have a digital downloadable product and once it's been purchased I want to send the buyer a unique link, I think it's great that you offer this is a standard part of your service.



What do I need to do in my seller admin to do this? (I mean what needs to be checked unchecked etc)



Thanks in advance for your help it's really appreciated.



Regards



seanmd1

Your so called Product Package feature is a horrendous piece of UI crap! It's a pathetic piece of UI design!!!!!!!!!!!!!!

Why is the FUCKING! Remote Product File URL box innacessible intermittently??