Ian wrote: > Hi list > > I am working as a contractor at a company that is using TRAK but the > main database that they are using is abroad and the connectivity > is ... well poor to say the least. > > As it stands at the moment, the staff lose a lot of time prepating > their submissions, clicking submit/commit and watching it time out > with the poor connectivity. Getting this fixed at the head office is > apprently a bit of a no-go since we're a tiny outlying branch and the > tech guys #1 issue is supporting local users. > > So .... I was wondering how hard it would be set up a local TRAK > server and just schedule that to commit to the foreign server every 60 > mins or so? Even every couple of hours would be OK - it is not time > critical data. I don't know if we would need some sort of 'wrapper' to > check for succesful commits or not? > > I looked at mirroring but that appears to be a read only local copy of > the database, which is not what we are after. > > If you need any more information, I am back on site tomorrow and can > investigate further. >
Just for the record, it's a possible long term goal for Trac (see http://trac.edgewall.org/ticket/1465). If you feel like trying experimental systems, you'll find in this ticket a link to Fossil that you may find useful. If you try it out, please report back ;-) -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
