Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 1

CouchDb is a distributed document database system with bi-directional replication. It makes it simple to build collaborative applications that can be replicated offline by users, with full interactivity (query, add, update, delete), and later "synced up" with everyone else's changes when back online.

4.74286
   
  0 reviews  |  113 users  |  135,581 lines of code  |  41 current contributors  |  Analyzed 2 days ago
 
 

SymmetricDS is web-enabled, database independent, data synchronization/replication software. It supports bi-directional and partial synchronization across heterogeneous databases in near real time. The software was designed to scale for a large number of databases, work across low-bandwidth ... [More] connections, and withstand periods of network outage. It was first built to replicate changes between "Retail Store" (POS) databases and a "Corporate" central database. [Less]

4.0
   
  0 reviews  |  4 users  |  77,699 lines of code  |  5 current contributors  |  Analyzed 4 days ago
 
 

What is TsumuFS?TsumuFS is a disconnected, offline caching filesystem layer on top of NFS in the spirit of fexd and other caching filesystems (like Coda or Intermezzo). While these other filesystems require specific server-side support, TsumuFS is designed to be simple and elegant by solving only ... [More] the caching issue, and not the filesystem protocol itself. GoalsReliability. Allow users to continue working on a locally saved copy of their files if the local nfs server goes away (ie: down) People efficient. Provide a way after the file server comes back up for all changes to be integrated to the filer seamlessly and without user interaction unless a conflict from a concurrent change has occurred. Network/Infrastructure efficiency. Provide for an alternative to moving users' home directories around the various global filers. Consistent user feedback. Provide timely and helpful information to the user of the state of the filesystem in the form of socket or /sys IPC. Direct control over the cached data. It should be possible to exclude files from the cache entirely, and to persistently keep a set of files in the cache. Non goalsTsumuFS should NOT reimplement the network filesystem protocol. NFS is tried and true, and well supported as-is on most architectures -- TsumuFS only augments the NFS layer. It should NOT provide policy or infrastructure for the encryption of the file store. TsumuFS should function at the VFS layer ONLY -- encryption of the underlying file store is up to the administrator. It should NOT implement an entire filesystem to store cached data and the state of TsumuFS's world. As TsumuFS functions at the VFS level, the underlying filesystems should be used for storage. [Less]

0
 
  0 reviews  |  0 users  |  5,081 lines of code  |  0 current contributors  |  Analyzed 3 days ago
 
 

With the current trend of offline applications and solutions as Joyent Slingshot or Rails2Exe to run a stand-alone offline client app written in Rails, we end up having a problem ahead of us: offline data gathering and synchronization back and forth to a main online server. There is virtually no ... [More] solution for that matter unless you use some proprietary and expensive package. Google Gears comes to mind but it acts more like a static client-side caching providing no real replication of data. So 'acts_as_replica' was really made to scratch my own itch. It was made for the scenario where you will have several clients working in an offline environment and then they'll connect at the end of the day to get new data from the server and also send back what it collected through out the day. This is a very opinionated software, meaning that it was not made to cover every single synchronization scenario in the world, but small and mid-sized solutions should benefit. It uses HTTP to wire both peers and up until now formats the payload packages in YAML. This plugin was very influenced by the plugin acts_as_syncable by Alex MacCaw. Actually I used his code as the initial structure but it's now very far departure from his original view. This project was done under the support of my current employer, Surgeworks. I am not done yet, so this is a work in progress. Any collaboration and ideas will be welcome. Read the HowToInstall, MustRead and HowToTest Wiki Pages for more information. And don't forget to download the Example Project so you can have a faster hands on. If you have any suggestions, doubts, ideas contact me at fabio.akita@surgeworks.com. Apr, 3rd, 2008 - Moving to GitI am abandoning Subversion management. I will leave this homepage behind but the source code here is frozen. Newer updates will be only at Github. http://github.com/akitaonrails/acts_as_replica/tree/master I am very late updating this code, sorry for that, I will try to make it more user friendlier now. Sep, 23th, 2007 - Lots of ChangesI just uploaded a batch of new features and bug fixes to the plugin. I finally had time to test it further and I am much more confident about it. The Sync table was renamed to Replica - the daemons plugin seems to complain with this name Added RemoteMachine table. Now the handshake process exchange Machine IDs (UUID), and the new Replica table keeps track of each machine_id. That way, the transactions are no longer bound to a single User in a single client App. The same username can be used in any client installation and still be able to safely replicate data back and forth. The client and server no longer uses a timestamp (in the last_synced columns of User and RemoteClient) to track each others transaction log entry points. It has been replaced for a simple auto-increment integer number (the primary key for the new Replica table). syncable.yml was deprecated in favor of a SyncSetting singleton Model. You will have to create your own administration screen, though. It was asserted that SSL connection do works Created a proper script/generator instead of the old manual file copy operation. I deprecated the use of the old Engine plugin because it was too buggy with dependency loading. Added support for background jobs triggered through a controller. Sample controller and views included. It is cross platform as well. In nix I use the good ol' system() call and in Win32, the Process.create method. You can control what's happening tailing the log/replica.log file Added experimental application self-upgrade. lib/daemons/upgrade.rb is a new background job that calls svn cleanup, svn update and rake db:migrate. That way the application can be updated remotely without direct SSH connection to the server Batch control was finalized and tested: the syncs_helper.rb now implements a run_sync method that controls run_upload and run_download. Each can read its local batch_limit settings (see SyncSetting). Then it can retrive XX number of rows at a time. This can be used to refine transfer using slow connections, so to avoid timeouts. Jul, 8th 2007 - New Project MemberI just added Marcus Derencius, a good friend of mine, as a contributor. He pointed out somethings that we could add to this project: The User class is hardcoded. We need to make this configurable to allow for other authentication plugins that doesn't use a model named 'User' Generate automated RDoc documentation Add support for Rake tasks. And actually Slingshot expects to find a :up and :down tasks in its GUI Devise some cronjob like scheduled task to actively check whether the network is on or not and automatically start replication in the background, thus avoiding having to replication too big packages only at the end of the day Put in some connection checking before starting the 'perform_sync' process. If you start it without having the server part online, the client process simply hangs and you have to forcefully kill it. Jul, 17th 2007 - Merged with UserstampI realized that the vanilla Userstamp plugin doesn't work properly with this plugin. Until I devise a better way, I merged the userstamp.rb in the lib folder of the plugin. The belongs_to proxy method fails in some cases and the usage of the UUID can conflict as well. So delete the original userstamp plugin and use the one in this plugin. [Less]

0
 
  0 reviews  |  0 users  |  2,736 lines of code  |  0 current contributors  |  Analyzed 7 days ago
 
 

Daffodil Replicator team today released Replicator v2.0 (beta) with support for Firebird to Firebird data replication, in addition to significant performance enhancements. With v2.0, all replication operations can be performed faster, when compared to earlier Replicator versions.   The new ... [More] features introduced in Replicator v2.0 are:   Support for Firebird: Replicator v2.0 can be used with Firebird database. It supports bi-directional data synchronization between Firebird (Server) database to multiple Firebird (Client) databases. The version does not provide the functionality of Firebird data replication to heterogeneous database servers. This functionality will be introduced in future Replicator versions.   Partial Tables Replication: Partial Table Replication allows a user to ignore specific columns in a publisher database table. It provides the flexibility to disregard data (residing in publisher database columns) that is not required on the client side, hence making the replication operation more efficient.   Cyclic Tables Replication: Replicator v2.0 can be used with complex database structures where tables have cyclical dependencies. The previous replication versions could not replicate the tables that hold references to each other.   In regards to performance, with Replicator v2.0, the XML file creation process has been reviewed and optimized. The new process drastically reduces the time taken in capturing the insertion, deletion and updation of records from Replicator Shadow tables and transmitting the same to the target database server. Major bug fixing related to tags issues in XML file, appending the foreign key constraint and creation of transaction log file during Real time Replication has also been done. [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors  |  Analyzed 4 days ago
 
 

FsObserver is a simple CLR console application or service that can watch activity on the file system and take an action such as replication or execution of an application. The implementation is based on a tweaked instance of the FileSystemWatcher class.

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

BeyondSync is a PC based file synchronization utility. BeyondSync helps you "push" podcasts (and any other files) from your desktop directly to your windows mobile device (Pocket PC or Smartphone). You can set it up to automatically push only the new podcasts when your device is connected. ... [More] You can also use BeyondSync to synchronize any 2 PC folders. BeyondSync is a PC based application and does not require anything to be installed on the mobile device. [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

JEE Cluster Tools contains a set of usefull tools to help JEE developers with some cluster particularities. Was developed by Érol T. Stocchero and distributed by Érol Labs, Brazil. The two main features: - Singleton object em multiple JVM - Replication and synchronization of objects in cluster ... [More] environment JEE Cluster Tools uses Java RMI technology. [Less]

0
 
  0 reviews  |  0 users  |  423 lines of code  |  0 current contributors  |  Analyzed about 3 hours ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.