Excellent. Thanks for trying out SyncJammer. I've found it pretty useful for backing up my SourceJammer data via FTP to a remote server. I really hope you find it useful tool.
I definitely would like to make the application smarter and have it remove files and directories on the "target" side if those files have also been removed on the "source". This should be fairly simple for filesys mode, but more complex for ftp mode.
I'd also like to allow 2-way syncing, so that you can set up basic rules for whether to download a more up-to-date file from the "target" instead of overwriting it from the "source".
But I'm pretty busy with other stuff, so enhancements may be a little ways off. Unless you have an interest in participating in making SyncJammer more robust . . .
--Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Excellent. Glad it works for you. And please share your WebDAV module when it's complete!
--Rob
PS: One other enhancement I'm thinking of, in case you're interested. Right now syncjammer puts a sync.jam file into each directory that it syncs. This is actually a serialized object, which, as you may be aware, causes some problems when you want to make changes to the class underlying the object that is serialized. That aside, some people may find it annoying to have these sync.jam files pop up in every directory. I'm thinking about moving this to some kind of config/sandbox directory that only SyncJammer messes with. Not sure exactly how I'd approach this, but I'd be interested in your thoughts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I tried building SyncJammer from the included sources. But soon I realised, that the utility stuff is missing.
Where can it be found ?
In the SourceJammer there are "similar" classes, but it seems as the naming has been reorganized....
I would try to solve the 1024bytes bug.....
Hi, Andre.
Sorry to be so slow in responding. I don't monitor this list as closely as I should. I'll look into this and see what's up.
--Rob
Thanks for the fixes.
The beta4 looks very nice.
Excellent. Thanks for trying out SyncJammer. I've found it pretty useful for backing up my SourceJammer data via FTP to a remote server. I really hope you find it useful tool.
I definitely would like to make the application smarter and have it remove files and directories on the "target" side if those files have also been removed on the "source". This should be fairly simple for filesys mode, but more complex for ftp mode.
I'd also like to allow 2-way syncing, so that you can set up basic rules for whether to download a more up-to-date file from the "target" instead of overwriting it from the "source".
But I'm pretty busy with other stuff, so enhancements may be a little ways off. Unless you have an interest in participating in making SyncJammer more robust . . .
--Rob
Actually syncjammer does what need.
But it could be possible that we have to sync against a WebDAV target in about 2 months.
So there is a chance that I will write a WebDAV tagret module.
Thats what I like about java, take a existing base and add new features as needed.
Excellent. Glad it works for you. And please share your WebDAV module when it's complete!
--Rob
PS: One other enhancement I'm thinking of, in case you're interested. Right now syncjammer puts a sync.jam file into each directory that it syncs. This is actually a serialized object, which, as you may be aware, causes some problems when you want to make changes to the class underlying the object that is serialized. That aside, some people may find it annoying to have these sync.jam files pop up in every directory. I'm thinking about moving this to some kind of config/sandbox directory that only SyncJammer messes with. Not sure exactly how I'd approach this, but I'd be interested in your thoughts.