Welcome Guest! To enable all features, please Login or Register.



Last Go to last post Unread Go to first unread post
#1 Posted : Thursday, July 5, 2007 10:36:24 AM(UTC)


Groups: Registered
Posts: 3

We are working with the .net components of version 15. We have created a basic DICOM "router" using these tools. And it works very well!

We have several clients asking about prioritizing a "send queue". They are all using different PACS/DICOM solutions, but they want the same thing. We are wondering if there is anyway to accomplish this with Leadtools Medical Suite SDK.

Basically they have limited bandwidth. As soon as they start to send a 1,500 image "cstore send" to a remote SCP server they end of with a small "wet read" (emergency) that needs to go immediately. Even if the solution is multithreaded (which many are not) the bandwidth that the 1,500 image study is taking up slows the send of the "wet read" considerably.

Is there a way to throttle down sends? Is there a way to prioritize? I know the SCP message has a priority on it...but is just seems to be a message priority and I am not sure what exactly it does.

Any insight or ideas would greatly be appreciated. We are finding as studies get larger and take longer, bandwidth contention is becoming a bigger issue for everyone.

Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads

Wanna join the discussion? Login to your LEADTOOLS Support accountor Register a new forum account.

#2 Posted : Wednesday, July 11, 2007 4:32:52 AM(UTC)


Groups: Registered, Tech Support
Posts: 207

Was thanked: 3 time(s) in 3 post(s)

As a DICOM Router you are in full control of what gets sent and what doesn't.  When sending a 1,500 frame image (cstore send) you are sending each frame as a separate C-Store request.  When an emergency request comes in, stop sending the C-Store request and send the emergency one. 

You can do this in the same or separate thread using the same or separate connection (some SCP's may only support one connect from one client at a time.)  Just create another connection and send the emergency request or kill the current connection and send re-connect to send the emergency thread.

There is nothing stopping you from doing this in the LEADTOOLS library.  This is completely Application Implementation.

Travis Montgomery
Senior Sales Engineer
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2024, Yet Another Forum.NET
This page was generated in 0.047 seconds.