Search found 9 matches
- Mon, 2013-09-16, 05:15
- Forum: DCMTK - General
- Topic: Can a C-STORE scp know when a complete study is received?
- Replies: 1
- Views: 3918
Can a C-STORE scp know when a complete study is received?
I am trying to implement a C-STORE SCP using DcmSCP. Is it possible for the SCP to determine when a complete study has been received? If the storage requests were cancelled mid-way through a study (e.g. by a C-CANCEL request to a C-MOVE SCP), then can the C-STORE SCP know that the study it has recei...
- Wed, 2012-12-05, 13:36
- Forum: DCMTK - General
- Topic: Graceful shutdown of DcmScp
- Replies: 4
- Views: 8795
Re: Graceful shutdown of DcmScp
> The function stopAfterCurrentAssociation() will cause the DcmSCP to stop listening after receiving the next association. I am writing a DICOM client, so the STORE SCP will only receive images that are requested from a server using GET, and that means there are very unlikely to be any incoming asso...
- Tue, 2012-11-20, 18:05
- Forum: DCMTK - General
- Topic: Graceful shutdown of DcmScp
- Replies: 4
- Views: 8795
Re: Graceful shutdown of DcmScp
Hi omarelgazzar,
Yes I have done that. But the listen() function still blocks while waiting for an association. If no more incoming connections are received then listen() never returns.
Yes I have done that. But the listen() function still blocks while waiting for an association. If no more incoming connections are received then listen() never returns.
- Fri, 2012-11-16, 20:50
- Forum: DCMTK - General
- Topic: Graceful shutdown of DcmScp
- Replies: 4
- Views: 8795
Graceful shutdown of DcmScp
I am writing a C-STORE SCP using the DcmSCP class and I am unable to find a way to gracefully shutdown the SCP. If I use the blocking connection mode, then the method DcmSCP::listen() never returns, so I have to forcefully terminate the thread. Alternatively, if I use the non-blocking connection mod...
- Mon, 2008-06-16, 15:59
- Forum: DCMTK - General
- Topic: The format of the DiPixel data returned by getInterData()
- Replies: 1
- Views: 3969
The format of the DiPixel data returned by getInterData()
Hi, I am trying to access the pixel data for a DicomImage by using the getInterData function, but I cannot work out the format. I tried using a function like this, but it causes a memory access violation: Uint16 samplePixel( DicomImage* dcmImage, unsigned x, unsigned y) { const DiPixel* interData = ...
- Wed, 2004-11-10, 11:09
- Forum: DCMTK - Installation
- Topic: Problems linking DCMTK 3.5.3 with Visual Studio .NET 2003
- Replies: 8
- Views: 22935
Re: Problems linking DCMTK 3.5.3 with Visual Studio .NET 2003
From the project dcmprscu, for example, all of the following directories are included in the Additional Library Directories setting: dcmtk-3.5.3\dcmpstat\$(INTDIR); dcmtk-3.5.3\dcmpstat\; dcmtk-3.5.3\ofstd\$(INTDIR); dcmtk-3.5.3\ofstd\; dcmtk-3.5.3\dcmdata\$(INTDIR); dcmtk-3.5.3\dcmdata\; dcmtk-3.5....
- Tue, 2004-11-09, 22:31
- Forum: DCMTK - Installation
- Topic: Problems linking DCMTK 3.5.3 with Visual Studio .NET 2003
- Replies: 8
- Views: 22935
Problems linking DCMTK 3.5.3 with Visual Studio .NET 2003
Hi, I have now managed to build DCMTK using Microsoft Visual Studio .NET 2003 and CMake 2.0.5, but I had a problem that stumped me for hours, so I thought I'd share the solution. My problem was that all of the apps in the dcmpstat directory failed to link, reporting the error: LINK : fatal error LNK...
- Tue, 2004-11-09, 21:45
- Forum: DCMTK - General
- Topic: Serious security issues with DCMTK?
- Replies: 2
- Views: 7690
Re: Serious security issues with DCMTK?
Thanks for the reassurance
Marcus
Marcus
- Tue, 2004-11-09, 14:06
- Forum: DCMTK - General
- Topic: Serious security issues with DCMTK?
- Replies: 2
- Views: 7690
Serious security issues with DCMTK?
I've noticed that the latest version of DCMTK is linked against libpng-1.2.5 and openssl-0.9.7d. From their web sites it appears that these versions of the libraries have security issues, does this mean that DCMTK software that has not been updated will also be vulnerable? The relevant security warn...