ActiveX storing data to be picked up by another ActiveX later?
-
I'm developing an ActiveX component, which is used on web pages. When user enters a page page, the ActiveX is loaded and when the user moves to another page, the activeX component terminates. However when user goes to another page, I must be able to transfer some data from the current instance of the ActiveX component to the next instance of it. I'm currently using cookies for this, but that is not a good solution for various reasons. What other ways are there to transfer the data? :confused: Is there some windows interface (servic) which I can use to temporarly store data, so that the data can then later be picked up by another ActiveX instance.
-
I'm developing an ActiveX component, which is used on web pages. When user enters a page page, the ActiveX is loaded and when the user moves to another page, the activeX component terminates. However when user goes to another page, I must be able to transfer some data from the current instance of the ActiveX component to the next instance of it. I'm currently using cookies for this, but that is not a good solution for various reasons. What other ways are there to transfer the data? :confused: Is there some windows interface (servic) which I can use to temporarly store data, so that the data can then later be picked up by another ActiveX instance.
Why can't you use local file? Temporary folder maybe good place... You can also overload OnFinalRelease or add extra LoadLibrary, so instance of your control or module will continue to stay in memory, even after IE Document Releases it... Also, as I recall CoFreeUnusedLibraries implemented by MSFT has a delay unload time of about 10 minutes -- so you can just use that -- your module stays in memory for 10 minutes, even after last instance of your control is realeased. So, you can use that by storing shared data as a static data or member of CWinApp class... Also, you can implement your own DllCanUnloadNow(void) -- just return S_FALSE -- that will guarantee that your module will stay in memory forever... "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me
-
Why can't you use local file? Temporary folder maybe good place... You can also overload OnFinalRelease or add extra LoadLibrary, so instance of your control or module will continue to stay in memory, even after IE Document Releases it... Also, as I recall CoFreeUnusedLibraries implemented by MSFT has a delay unload time of about 10 minutes -- so you can just use that -- your module stays in memory for 10 minutes, even after last instance of your control is realeased. So, you can use that by storing shared data as a static data or member of CWinApp class... Also, you can implement your own DllCanUnloadNow(void) -- just return S_FALSE -- that will guarantee that your module will stay in memory forever... "...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..." Me