Databases
StackOverflow2013
Postsdbo
POArchitecture of a Dropbox-like Windows client
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POArchitecture of a Dropbox-like Windows client
    primarykey
    data
    text
    <p>How would you design a windows client for a dropbox type syncronization system, using .NET as the base platform?</p> <p>The client communicates with the server using HTTP (json) for sync metadata, user info etc., and uses rsync for the actual file transmission. There should be a main interface window, a GUI accessible from the system tray (and always active there for notifications), and a Shell Extension for context menu and icon integration.</p> <p>GUI could be a standalone Windows Forms (or WPF) application, minimized to tray by default. The Shell Extension must be a standalone DLL registered with the explorer process. How about the core client functionality for communication with the server and for file transmission, and monitoring of the file system changes? </p> <p>What is the best way to implement this? As a separate application, a DLL containing the functions required, or a background windows service that both the GUI and the shell extension call when necessary? Or something else other than the 3 mentioned?</p> <p>One of the problems could be the necessity for the core functions to call (execute) an external process, the rsync.exe, for file transmission. Also, where ever the core functions are, the Shell Extension DLL must be able to use them.</p> <p>Are there any implementation or design details somewhere for the actual dropbox windows client? All that I could find was that it is is written in python, seems to use a sqlite3 database to index files and subversion and RSync internally to manage revision control.</p> <p>EDIT: Also, I forgot another aproach - .NET remoting. The client application would expose the methods for server communication the Shell Extension could use it.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMr.C64
    1. USigorbel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POArchitecture of a Dropbox-like Windows client
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POArchitecture of a Dropbox-like Windows client
      1. USmichael
      1. VTFavorite
    1. COIs this an always On service you're looking for or something that starts and stops when the user stops? What do you do if there is a vision mismatch or a network interruption those things might be more important then the way the app is build.
      singulars
      1. POArchitecture of a Dropbox-like Windows client
      1. USCodingBarfield
    2. COYes, you are correct. The always on part should be true only for the filesystem monitoring of the "dropbox" folder. The data transmission over the network should just be called on demand. The version mismatch is app specific logic, and that should also be handled in the functions that do the actual syncronization. Anyway, valid points, and they are being handled in the UX design and should be taken into consideration while doing the initial app architecture design.
      singulars
      1. POArchitecture of a Dropbox-like Windows client
      1. USigorbel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload