|
Main New Development v 124
Sissle
The improvement in layout of Sissle was suggested by a customer H Strand, StrandControl, LLC, www.homedomination.com
Linkage to the new Sissle NSE module.
Many internal improvements.
An extension to Windows Explorer - Sissle NSE
Navigation within Amazon S3 using Windows Explorer.
Drag and Drop
to and from explorer has been completed for Vista / XP / 7 (32 bit and 64 bit).
Advice: Use two Windows Explorers one showing the source folder and the other showing the destination folder.
Try with your own applications opening, using and saving files
directly from Amazon S3. The key word here is try, this is not
guaranteed to work now or in the future. With a certain amount of
luck of how the application has been written, this is possible.
Carefully
try this, for example open a document on Amazon S3 with say "Open
Office" edit, save it. When you click open in the application "Sissle
S3" earth ball will appear under computer for you to navigate to.
Important: Sissle NSE opening and saving files directly on Amazon S3 with applications.
Firstly an explanation of how this is achieved technically which will lead us directly to the main problem.
Sissle NSE is an extension to windows explorer, which is why it will appear in the open dialog.
Applications can not access Amazon S3 directly, so there has to be some trickery *.
Sissle NSE intercepts the "ok" of the "open file" dialog and transfers
the selected file to a temporary folder on disk and then finishes the
open dialog by altering the file location to the file now in the
temporary folder.
Here lies the problem you may stumble over. Next time you use your
application, the "recent files" will show your file in the temporary
folder. This file will exist and most probably be most up to date
version, but when you save this file it will only be written to the
temporary folder not to Amazon S3.
It is important each time you open a file in S3 that you slavishly navigate to it on S3 and please ignore any recent lists.
On save Sissle notices that the file has changed and writes it back to
S3. Application can lock files and this will stop Sissle from doing its
job of writing back to S3. How different applications are written is
impossible to know, therefore there is a certain amount of luck in this
mechanism working.
* I believe some people have written disk drivers for S3 and so making this statement untrue.
|
