Robert Sachunsky

Sure, let's wait for his commentary first, then if necessary switch to AGPL for the whole lot.

> Sure, let's wait for his commentary first, then if necessary switch to AGPL for the whole lot. (But perhaps we should ask the original contributors if that's ok –...

@tfmorris thanks for clarifying this, and for https://github.com/kba/pylsd/pull/4! > Consideration might also be given to updating to 1.6 and switching to a memory-based API instead of the current file-based hack....

I would indeed – just give me some time.

> But how will the Processing Server know which processing requests are chained together in a workflow? Since there is already a differentiation between `DBProcessorJob` (processing endpoint) and `WorkflowJobDB` (workflow...

> but the Processing Server is just a proxy (with some validation on top) as it is now and has no other role. The PS is the only one creating...

> So maybe utilizing a Python list of `OcrdProcessingMessage` as an internal queue structure for a specific `workspace_id` is more straightforward? In the end, it's still an internal queue for...

> > So maybe utilizing a Python list of `OcrdProcessingMessage` as an internal queue structure for a specific `workspace_id` is more straightforward? In the end, it's still an internal queue...

> There is still no clear vision of the METS Server's location on the Network architecture as partially discussed in #1035. Yes, but IMO we have now come to the...

> > what is the point of spinning up a METS Server for each processing step and tearing it down afterwards? > > For internal page-wise processing on the worker...