On 8/23/2010 6:44 PM, Markus wrote: > Hi, > > sorry for the delay of my answer. > > On Thu, Aug 12, 2010 at 5:21 PM, vjimw <im.a.machobea...@gmail.com > <mailto:im.a.machobea...@gmail.com>> wrote: > > When we upload files to the CDN, we store that path with the object. > Then we override the widget for the file so we can server the file > directly from the CDN using that field. Would that work for you? > > > If I understand it correctly for this solution the CDN has to be > accessible from the internet, right? > > My problem is, that the CDN is only local available and the only > connection to the rest of the world goes through the Django app. So as > far as I understand it I would need something like a "pipe". On the one > end my local CDN in the middle Django and on the other end the internet > user who wants to download/upload a file. Django than reads from the CDN > and forward it directly to the user. > > Is this possible? Is this what your solution does, maybe I have not > understand it correctly? In this case maybe you can elaborate a little bit? > > best wishes & Thanks, > Markus > Surely the whole point of a content delivery network is to act as a proxy for the data source. Buffering it through Django means it's no longer a CDN, it's just a data store.
regards Steve -- DjangoCon US 2010 September 7-9 http://djangocon.us/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
