Posted by Barbara Brazil on September 17, 2018 at 13:03:14:
In Reply to: Re: XAP control file...> posted by Barbara Brazil on September 17, 2018 at 07:16:12:
It looks like fixing the XAP documentation and getting all the demo programs available again is going to be a big project. I'm going to save this one for Jim when he returns from vacation :-)
In the meantime, I went thru several pages and compiled this list of #XAP commands for you:
The CLOSE command tells Comet to stop listening on the XAP gateway (in effect, resetting
LOGFILE pathname[,cycle | ,erase]
The cycle option keeps up to 7 generations of the log file.
Specifies the port for XAP to listen on. Port 80 will be used by default.
This will direct XAP to use direct Windows calls rather than going through the file server. The default is to use the file server. Logging however always uses Windows calls because of stack space limitations.
This is used to set the expiration date for an eComet Context cookie. x is number; T is M|D|H, (for example 5M for 5 minutes); optional ProgramName is program to run when a new cookie is created (for example a relogin program). Without ProgramName, the normal XAP program is run with ClearCommon. Previously cookies expired only when the browser was closed. Now the cookies are persistent. Without the EXPIRE command cookies will be session cookies as they were before this enhancement. You can delete a cookie by setting an expiration date in the past.
Don't know what this is supposed to do, but it was added as a new command for Comet32. Anybody know? It sounds like it turns on the Comet32 TRACE window you'd get if you said TRACE ON in your IB program.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.