This will require some rethinking and retooling in both the JS frontend and the go backend.
JS upload could take turns using XHR with separate upload bars, or, perhaps, it could do all at once and aggregate the upload totals (or take turns and aggregate as well).
The frontend would be easy enough, but there needs to be a way to list multiple entries to a user.
Perhaps handling via GET like /?<image1>&<image2>&<image3> to present either a thumbnail list or an anchor list.
This will require some rethinking and retooling in both the JS frontend and the go backend.
JS upload could take turns using XHR with separate upload bars, or, perhaps, it could do all at once and aggregate the upload totals (or take turns and aggregate as well).
The frontend would be easy enough, but there needs to be a way to list multiple entries to a user.
Perhaps handling via GET like
/?<image1>&<image2>&<image3>to present either a thumbnail list or an anchor list.