View in #ohif on Slack
@Scott_L: hey, I had a question about the static wado serving. Basically, I’m running ohif in an electron environment and rather then use webdicom over a network im looking at the best way to store and load the dicom files locally for the viewer. I’m quite sure using the /local endpoint functionality i could piece together a data layer to manage this, im just wondering if theres a better way like the static wado creator. If i convert the dicom to dicomweb using the static creator before sending to a client, can i just stream that over IPC? Basically, if it exists, where would i find how to load a webdicom file directly into the viewer rather than networked stream. Thanks!
@Bill_Wallace: If you just run a local proxy server, then you can fetch the data ahead of time from a real DICOMweb server. Static DICOMweb has most of that functionality ready, except it fetches over DIMSE C-Find/C-Move, but I think just fetching to a proxy server if the data isn’t found woudn’t be hard.
Then, if the data isn’t found int he proxy, you just have the proxy server fetch it at the request time.
The studies requests could be cached for a minute or two, but not longer than that.
@Scott_L: im wondering if there would be any actual benfit for me to do that given the potential overhead of running a proxy server. Ive created a custom worklist that uses metadata im providing outside of webdicom, and my initital plan was to just send the dcm files and load them directly. The compression and optimization for ohif was what had me considering using static webdicom but im not overly keen on having to run another server locally on each client. I’m likely missing something obvious though
I’m really looking for the most efficient way to load the dicom files, while allowing for offline viewing