Hi all, the online demo has been very good in showing the potential of the protocol. Also it showed that some procedures were missing some data that might be important to display.
Currently this weakness is the EMR.Image.URL.List. In its current form, it only returns an array of URL strings. But information about the image being shown on the browser are not available. Using other procedure calls to retrieve the info for each image would be too inefficient. So I propose that we discard the EMR.Image.URL.List but instead use a new procedure call EMR.Image.List which returns an array of struct that contains the following key-value pairs: nr = primary key to image data url = url string date_shot = date image taken date_upload = date image uploaded notes = notes about the image (diagnosis, comments, questions, etc.) uploader = uploader id You will notice that the image binary data is not returned. The reason is to reduce the data payload. When the url is given to the browser, the browser will retrieve the binary data anyway and in a much more efficient way. This way, we avoid redundant transfer of potentially large data volume. Comments and counterproposals will be highly appreciated. Thanks in advance, elpidio ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Hxp-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hxp-developers
