Spec image upload + pipeline trigger flow #16

New issue

Closed

opened 2026-06-25 03:11:38 +00:00 by Mark · 0 comments

Mark commented

2026-06-25 03:11:38 +00:00

Owner

Workspace takes an image and runs the digitize pipeline. The flow today is entirely in-browser (Fabric.js). The service-backed flow needs:

Multipart upload of the image to the service
Pipeline trigger (POST /v1/digitize per the easystitch-client contract)
Long-running request handling -- pipeline takes seconds, possibly minutes for large images. Browser fetch will time out. Options: (a) sync request with generous client timeout, (b) async job submission + polling, (c) webhook/websocket.
Where the result lands: client-side state, or persisted via the designs API?

Acceptance: a working upload+trigger flow from Workspace.tsx through the easystitch-client to the service, with the long-running-request strategy decided and documented.

Workspace takes an image and runs the digitize pipeline. The flow today is entirely in-browser (Fabric.js). The service-backed flow needs: - Multipart upload of the image to the service - Pipeline trigger (`POST /v1/digitize` per the easystitch-client contract) - Long-running request handling -- pipeline takes seconds, possibly minutes for large images. Browser fetch will time out. Options: (a) sync request with generous client timeout, (b) async job submission + polling, (c) webhook/websocket. - Where the result lands: client-side state, or persisted via the designs API? Acceptance: a working upload+trigger flow from Workspace.tsx through the easystitch-client to the service, with the long-running-request strategy decided and documented.