Re: Homegrown synchronization

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"rdemyan" <rdemyan@xxxxxxxxxxx> wrote in
news:1167806825.091163.59480@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

But that's only the date and time of the *file*, not the data
and time of the updates included within it. If somebody
doesn't synch until a couple of days after they do updates,
the file could be dated several days after the actual data,
and that means you can't process them in order of file date --
you'd want to process them in the order that the changes were
made.

No, actually each update file has the user's logon ID and the
date which the update file was created in the file name. So I
do know when the update file was created and by whom.

But that doesn't tell you the date of the *data* changes in it.
Now, if you can count on the upload completing each time the user
exits the app, perhaps that's OK. But I'm not sure that's safe.

Each update DB that my code creates from the changes made by a
user to their loca copy of the backend file is unique and only
counts for that session. It is never reused.

That's not the point. The point is that you're assuming there is
never any latency between the upload and the updates it includes.

So the user name and date of the update
file I think do pretty much reflect the date of the data changes.
Update files are not reused. After the update file is sent to the
server, a copy of that update file is put into an archive folder.
Each session, MyApp creates a new update file with the USER ID and
the start date/time of the session.

If I understand your suggestion (and frankly I don't think I do),
what immediately comes to mind is that I'm passing a large file
(the production backend) around from server to remote and back.
My approach has been to pass a small file up to the server and
then pass the updated large file back down.

No, I'm not suggesting that at all. I'm suggesting that, rather than
depending on the data of the filename, instead processing the
records in the uploaded update file one by one against their
corresponding records and using the dates *in the records
themselves* to decide what to do with the data in them.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Re: http Upload über FP Srv. Ext.
    ... zum http Upload verwendet und den Anonymen Zugriff für den Upload ... Windows 2003 Web Server Edition ... > Session festgesetzt ... einem derart geschützten Netzwerk befinden das ausschließlich http Zugriff ...
    (microsoft.public.de.frontpage)
  • setcookie() Expiration
    ... I am having problems setting a cookie to expire in the future rather ... than at end of session on a particular server. ... I can upload the code ... to another server and the cookie expiration is correct. ...
    (comp.lang.php)
  • Re: File Upload - Security Issues
    ... You want to upload a file for what reason and ... these viruses have less chance of being able to execute (even if succeeded ... :> file and what pitfalls you see re: security might be helpful on this ... :>: files to an IIS server that doesn't have MS Office actually installed? ...
    (microsoft.public.scripting.vbscript)
  • Re: File Upload - Security Issues
    ... uploaded and the user could upload any or all of these in theory. ... There is no one product that can give you 100% security, ... > Code doesn't execute in local memory space unless remote user has rights ... > You don't have MS Office installed on the server. ...
    (microsoft.public.scripting.vbscript)
  • pure-ftp nologin
    ... I have a server running FreeBSD 6.3. ... # If you want to enable PAM authentication, ... AnonymousCanCreateDirs no ... # Disallow anonymous users to upload new files ...
    (comp.unix.bsd.freebsd.misc)