That could work. With this thinking, we could even do away with the report generator. Instead, image generation and file generation would be separate weewx services. Each would invoke its own FTP session when done. Because the set of generated files are disjoint, there would be no duplicated effort (although there could be multiple simultaneous FTP sessions).
I believe the module ftpupload is pretty standalone. There's nothing in there that depends on the report generator framework. -tk On Mon, Feb 13, 2017 at 9:44 AM, mwall <[email protected]> wrote: > On Monday, February 13, 2017 at 12:19:40 PM UTC-5, Tom Keffer wrote: >> >> someone should write an rsync and an ftp service that can be bound to >>> NEW_LOOP_PACKET. it could use the same code used by the ftp/rsync reports, >>> just wrapped in a StdService instead of report generator. >>> >> >> The problem with this approach is that then you need some sort of lock >> for the FTP service, so it knows when the reporting thread is done. >> >> Hence the decision to put the FTP and reporting in the same thread, run >> by the same generator. >> > > that makes sense. and it works really well for reports. > > but there is a need for a general approach to doing transfer/sync outside > of the StdReport framework. > > what if the ftp/rsync were a black box that any service could initiate? > for example, as soon as it finished its 'work', the crt extension could > start an ftp/rsync process. or a json or csv extension, as soon as they > finish writing, could start an ftp/rsync process. > > so the notion of a transfer/sync could be a feature that any service could > easily implement, and there would be a standard 'transfer/sync-parameters' > stanza analogous to database bindings. > > (doing real-time feeds with mqtt, influx, emoncms, etc gets the job done > but with a totally different approach) > > m > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
