Safe for scripting/initialization
-
Hi Everybody! I have developed an activeX control that instantiates a "in proc server" which accesses the sound card using DirectX. Neither the control nor the data component (collected from the sound card) write to any files in the user HD. I intend to deploy this control on the internet, so my question is: Can i mark this control and the component as safe for scripting/Initialization? On which conditions can i mark a control with these categories? Thanks in advance, Luís Teixeira
-
Hi Everybody! I have developed an activeX control that instantiates a "in proc server" which accesses the sound card using DirectX. Neither the control nor the data component (collected from the sound card) write to any files in the user HD. I intend to deploy this control on the internet, so my question is: Can i mark this control and the component as safe for scripting/Initialization? On which conditions can i mark a control with these categories? Thanks in advance, Luís Teixeira
Hi, A safe control must not perform disk IO or access the memory or registers of a machine directly. As I know DirectX is using direct memory access. But it's up to you to make a final decision... Regards, Alex Gorev, Dundas Software.
-
Hi, A safe control must not perform disk IO or access the memory or registers of a machine directly. As I know DirectX is using direct memory access. But it's up to you to make a final decision... Regards, Alex Gorev, Dundas Software.
So you're saying that you wouldn't mark the control as safe if it is using DirectX. But this control needs to access the sound card for data. I guess that using the multimedia functions of the WIN32 API has the same problem than DirectX, which leaves me no chance to make it a safe control. Thanks so much, Alex! Luís Teixeira