login
Search
I had an idea which I believe would help all users if implemented in the OS level. Currently if you want to manipulate a file/resource which is a remote computer, it is not easy to do it. you should know the application that handles that protocol and any switches you may need for that application. But there is already an answer to that. You can use URIs to refer to these resources.
e.g. when you want to copy a file from a remote computer to your computer you should use
scp user@computer.domain.com:/path/testfile ~
alternatively if the OS was able to understand URIs and invoke the appropriate application then you could just type
cp ssh://user@computer.domain.com[:port]/path/testfile ~
in order to have this functionality you need a central place which resolves a protocol name to the application which can handle it and then the application depending on the type of the resource can handle it appropriately.
I would like to your your comments on this suggestion.
Hi, This looks like a grea
Hi,
This looks like a great idea. It would create a powerful and quite generic way of doing things. One could make a config file somewhere that states what tool should be used for which protocol and how it is supposed to be used. It would also be nice to have way to relay the command-line options of those tools in some way... There should also be way to state what restrictions exist for certain protocols. for example with HTTP/1.0 one cannot save files. etc.
great idea!
greetz,
Roel Meeuws, BSc
Delft University of Technology
Netherlands
>There should also be way to
>There should also be way to state what restrictions exist for certain
>protocols. for example with HTTP/1.0 one cannot save files. etc
maybe you don't need this because you can have an alternative . For example you can define that writing to http:// is a get or post action. Anyway if an action is not supported it can just fail, but this will be handled by the application that handles each protocol and not by the OS.
Lufs?
Look for lufs "linux userspace file system", or similar words. Things like this have been implemented already.
right
you can also look at the gnomevfs library.
anyway this kind of functions should be in user-space and not kernel-space.