Server-Side Programming

Well, basically - nothing. You don't need to do anything special in order to incorporate @ctiVideoWeb in your project. From the webserver's perspective, the @ctiVideoWeb control behaves exactly like a normal HTML form, containing <INPUT type="file> tag. The only difference is, that instead of uploading a file from the visitor's hard drive, the control uploads a video frame or full-motion video clip.

The control will look as if the user has clicked the "Submit" button on the following page:

<FORM name="actiVideoWeb" method="POST" action="uploadvideo.asp">
<INPUT type="file" name="ActivideoControl">
<INPUT type="file" name="ActivideoControl2">
<INPUT type="text" name="SessionID">
<INPUT type="submit" value="Submit">
</FORM>

The ActivideoControl form field contains the first video/image file, the ActivideoControl2 form field contains the second video/image file (optional, only if ASFVideoStreams property was set to 2) and the SessionID form field will contain the value of the SessionID parameter of the control.

From here on, it's totally up to you to decide how you handle the uploaded files. One thing, that is worth mentioning is, that no matter what webpage you return to the control, it will not be shown on screen or executed by the Javascript/VBScript interpreters. This also includes the headers of the page, so if you want to show a result or redirect the user to another page, you'll have to use the webpage, specified in the URLCaptureFinished parameter of the control. The script, that handles the uploads does only that - handles the uploads (because the script was called from within the control, not within the browser). No interaction with the user can be done at this time.