health-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Health-dev] [task #15167] Orthanc DICOM module


From: Chris Zimmerman
Subject: Re: [Health-dev] [task #15167] Orthanc DICOM module
Date: Fri, 01 Feb 2019 21:00:20 +0000

Thanks all!

It is a trytond-cron job - so an internal one. Although, still need to run 
trytond-cron. I was trying to figure out a better way to sync, but polling 
seemed reasonable considering the non-blocking changes endpoint provided by the 
REST API.

C


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, February 1, 2019 1:47 AM, Mathias Behrle <address@hidden> wrote:

> * Axel Braun: " Re: [Health-dev] [task #15167] Orthanc DICOM module" (Fri, 01
> Feb 2019 09:27:52 +0100):
>
> > very good news!
>
> Thanks a lot as well!
>
> > Am Freitag, 1. Februar 2019, 04:32:48 CET schrieb Chris Zimmerman:
> >
> > > Update of task #15167 (project health):
> > >
> > >         Percent Complete:                      0% => 30%
> > >                  Release:                    None => 3.4.0
> > >
> > >     _______________________________________________________
> > >
> > >
> > > Follow-up Comment #1:
> > > https://hg.savannah.gnu.org/hgweb/health/rev/7293408b973a
> > > Sync patients and studies from remote Orthanc servers via REST API
> > >
> > > -   trytond-cron job to poll changes endpoint(s) for new studies and
> > >     patients
> > >
> >
> > Many distributions move aways from cron in favor of systemd-timers. Maybe we
> > add this as well?
>
> 1.  It is trytond-cron, not cron. And it should be the internal trytond-cron 
> in
>     this case.
>
> 2.  Just as a side note: by far not all users are keen to use systemd or at 
> least
>     all parts of it...
>
>     Cheers
>     Mathias
>
>     --
>
>     Mathias Behrle
>     MBSolutions
>     Gilgenmatten 10 A
>     D-79114 Freiburg
>
>     Tel: +49(761)471023
>     Fax: +49(761)4770816
>     http://www.m9s.biz
>     UStIdNr: DE 142009020
>     PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
>     AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]