why not a allowing a simple file:///home/me/my.template kind of url? for simple installations this should do.
On Wed, Feb 19, 2014 at 11:42 PM, John Kinsella <j...@stratosec.co> wrote: > We definitely need to support more than http download. http upload sounds > interesting, but I'd love to see something more resilient for large uploads. > How 'bout specifying a "drop folder" type location on the mgmt server that > the server polls every 15 seconds for new files, then in the UI the user can > pick from the files shown there? Not as secure as your browser upload > pattern, though. > > Maybe use something like https://github.com/blueimp/jquery-file-upload that > allows resumable uploads? > > Just had the thought of maybe adding support for dropbox/box.net/etc. At that > point, an ImageFetch plugin hook starts to sound interesting. Adding a bit > torrent plugin could make getting the default templates quite snappy. :) > > > On Feb 19, 2014, at 2:12 PM, Chiradeep Vittal <chiradeep.vit...@citrix.com> > wrote: > >> Hi all, >> >> The fact that one has to have a HTTP server to host templates before the >> templates can be imported into secondary storage is an inconvenience. I am >> not sure how much of an inconvenience it is, but I was asked to detail the >> technical architecture, if it needed to be supported. Certainly, I can >> imagine for folks coming in contact with ACS for the first time, it might >> seem onerous to set up another web server. >> >> I've sketched a strawman proposal [1] to support browser-based uploads of >> templates and volumes to secondary storage. >> It is not yet a PROPOSAL since it is still raw (and I do not have time to >> work on this immediately). >> >> Please comment on this. >> [1] https://cwiki.apache.org/confluence/x/jY5cAg >> > -- Daan
