Posted by Robert G Laurin on September 05, 2013 at 08:51:16:
In Reply to: Re: Comet to<->from Visual Studio C++ posted by Barbara Brazil on September 03, 2013 at 06:47:37:
I recently had a similar issue with exchanging data back and forth between Comet and a Windows app.
Originally, there was the Universal Gateway that was simple and easy. Unfortunately it is not supported in Comet32. So I had to go another route, as suggested by Barb, and use the IP Gateway. After a week to tinkering, I now have a prototype VB program that can listen and handle multiple sockets from Comet and pass information back and forth between a 3rd party banking SDK.
In order to maintain PCI DSS, I included a 3DES encryption at both ends. So as long as the data is not written to disk, I am PCI compliant (and out of scope).
I chose to write it in VisualBasic because my C++ knowledge is null. It didn't matter that the SDK is in C#, with visual studio I was able to include it in my VB app.
You may want to look up that avenue; using IP Gateway (winsock), it works with Comet16 and Comet32.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.