<br><br><div class="gmail_quote">On 20 February 2012 23:05, Michael Gapczynski <span dir="ltr"><<a href="mailto:mtgap@owncloud.com">mtgap@owncloud.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div style="font-family:'Sans Serif';font-size:9pt;font-weight:400;font-style:normal"><div><div class="h5">
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">On Monday, February 20, 2012 10:48:03 PM Michael Grosser wrote:<br><br>On Feb 20, 2012 10:42 PM, "Frank Karlitschek" <<a href="mailto:karlitschek@kde.org" target="_blank"><span style="text-decoration:underline;color:#0057ae">karlitschek@kde.org</span></a>> wrote:<br>
><br>><br>> On 20.02.2012, at 22:11, Michael Gapczynski <<a href="mailto:mtgap@owncloud.com" target="_blank"><span style="text-decoration:underline;color:#0057ae">mtgap@owncloud.com</span></a>> wrote:<br>><br>
> > I've been thinking about mounting external storage to ownCloud and I've had a<br>> > few discussions with Robin about it. Now I'm looking for some feedback from<br>> > the community.<br>><br>
> Cool :-)<br>><br>><br>> > The general idea is to add support for mounting FTP and SMB to use as storage.<br>> > Writing a backend with PHP is possible for these, but they won't perform as<br>> > well as the native OS implementations. I think the best solution would be to<br>
> > recommend to sys admins to mount natively and provide a fallback to a PHP<br>> > backend if this isn't possible.<br>><br>> Yes. Protocols that are better supported by the OS should be handled by the OS.<br>
> We could still try to do a mount command and see what happens :-)<br>><br>><br>> > The other thing I need feedback on is deciding if normal users can mount<br>> > external storage. I see the need for enabling users to link ownCloud to<br>
> > services such as Dropbox, and Google Docs (Google Drive),<br>i think mounting gdocs, dropbox etc. we should use mounting them as unhosted/remote storage so unhosted and owncloud won't solve the proxy problem in two projects.<br>
but I'm not sure if<br>> > FTP and SMB should fit in with these. I'm also debating what is the best way<br>> > to integrate these into the filesystem. The simple way would be to mount it as<br>> > a directory and each service would be self contained. However, I can also<br>
> > invision having the files from Dropbox and Google Docs showing up in the root<br>> > of the filesystem with an indicator of their respective external locations.<br>> > During the upload or file creation process the user would be presented with a<br>
> > choice of where to store the file. This feels more natural to me than a<br>> > directory system and could prevent problems with locating files.<br>><br>> Hmm. I would use the OS tool for protocols like FTP, S3 or SMB<br>
><br>> Stuff like Dropbox. Google Docs/Drive, and other user services should be handled on a user level.<br>> So every user can mount their Google Docs and move their files around.<br>><br>> I donīt really know what you mean regarding the location of the files. Letīs say a user is using ownCloud and has already some files and folder uploaded. Than the users connect the ownCloud with an existing dropbox or Google Drive. Where do all the files show up that are already in dropbox or on Google? I think it is confusing if they all appear in the root directory. And what happens when a user has the same file or folder in ownCloud and dropbox?<br>
><br>> For me it makes more sense to mount a dropbox account into a folder, for example /dropbox. But perhaps thats only me :-)<br>><br>><br>><br>> > My main concern is creating a confusing environment for users with so many<br>
> > options for adding storage and a cluttered filesystem. Any thoughts?<br>><br>> Thats a good point. Mounting external filesystems is definitely an advanced option that shouldnīt be the first option on the settings page. :-)<br>
><br>><br>> Cheers<br>> Frank<br>><br>><br>><br>> Frank Karlitschek<br>> <a href="mailto:karlitschek@kde.org" target="_blank"><span style="text-decoration:underline;color:#0057ae">karlitschek@kde.org</span></a><br>
><br>><br>> _______________________________________________<br>> Owncloud mailing list<br>> <a href="mailto:Owncloud@kde.org" target="_blank"><span style="text-decoration:underline;color:#0057ae">Owncloud@kde.org</span></a><br>
> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank"><span style="text-decoration:underline;color:#0057ae">https://mail.kde.org/mailman/listinfo/owncloud</span></a><br></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
</div></div><p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Michael - I was under the impression that Unhosted could use any of the storage providers with ownCloud.</p></div></blockquote>
<div><br>Unhosted is targetting Couch and DAV for the initial roll out. GDocs, Amazon, Dropbox support is still experimental, but if anyone would like to volunteer to write a 'driver' that'd be helpful. I think we'll get the major ones in the end.<br>
<br>WRT to storage, the main requirement at the moment is to be able to store and retrieve documents. JSON format is a plus. CORS headers are a plus. RESTful API is a plus. <br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="font-family:'Sans Serif';font-size:9pt;font-weight:400;font-style:normal">
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Frank - I understand that it may be confusing when a bunch of files appear in your root directory and it may just add to the clutter I'm trying to avoid. My main reasoning for this is that it lets the user organize the files based on their own preference. Mounting it in one directory locks those files to that location and I feel that we aren't using ownCloud's potential in terms of filesystem abstraction. This also applies to sharing. I actually don't like the folder 'Shared' (the name choice isn't the best either) and would like to get rid of it in favor of putting files shared with you in the root directory. Of course, I think we should add a setting for the default location that these files end up, but allow some freedom for where they can be moved.</p>
<span class="HOEnZb"><font color="#888888">
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Michael <br><br></p></font></span></div><br>_______________________________________________<br>
Owncloud mailing list<br>
<a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
<br></blockquote></div><br>