Transferring data from an https:// server to a client.

[GKFC]

Hi,

Quite a long post.

BACKGROUND:

Currently we have a signup process here at work that involves the customer using a SWFKit application that launches them into an https:// server and then quits.

Once on the server the customer then signs up for our service, and at the end clicks on a button that downloads a file which configures their computer.

Unfortunately, on Windows XP SP2 this generates a potentially confusing and alarming warning popup box which we are now trying to avoid.

PROPOSED SOLUTION:

Instead of quitting, my application sits in the background minimised and waits for the user to click the final button and then acts accordingly.

IDEALLY:

When the user clicks the server side button some (session based) information is seemlessly loaded into my client side application. This application then dynamically creates and runs the relevant configuration file. Since this is done on the client side there should not be a warning box generated by SP2.

IF NOT:

When the user clicks the server side button it quits the browser and launches my minimised application. From there, the user enters information and the configuration file is generated and run. Again this would be clientside to avoid the SP2 message.

Any ideas on possible approaches to this? I am still trying to figure out the best way of doing this. ActiveX springs to mind.

Cheers,

G.

[SWFKit]

How about a embedded web browser in your application? when the user click the last button (this will trigger an event) you can download the configuration file and run it.

[GKFC]

Hi thanks for reply.

Hmmm, not really, the idea is to avoid any file download at all. The downloading of the configuration file is the source of the problem. The idea is to move that step of the installation to the clientside.

Even if I was to code a new browser, at the moment the SWFKit application launches an .isp file that pre-configures Windows and dials our customer into our https server. This .isp file then uses IE in kiosk mode.

That adds a further element of complication into the whole process.

To get around that would mean programatically replicating the functionality of the .isp file aswell which doesn't sound too appealing....

I am still brainstorming this idea and so any ideas would be great.

Cheers,

G.