Home About Us Contact Support Careers Resellers Customer Login









ColdFusion

Questions and Answers

Q. Can I set the default document to "home.cfm"?
A. Yes

Q. Can I disable directory browsing?
A. Yes

Q. Can I setup scheduled tasks (ie. can I use the tag)?
A. Yes

Q. Can I use the CFCONTENT tag?
A. Yes

Q. Can visitors to the the web site upload files (into my web space)?
A. We can configure any web space folder to be accessible (have read/write access) from the web server point of view.

Q. Can I use CFFILE to upload, copy, rename and delete files?
A. Yes

Q. Can I send email from within my CF tags?
A. Yes

Q. In fact, are there any restrictions on any other CF tags?
A. We allow execution of the following tags: CFFILE, CFOBJECT and CFDIRECTORY

Q. Is the CF administrator available at all?
A. Because of security considerations, we don't allow access to CF administrator page. You can submit any CF configuration request to our main support e-mail address support@datagate.co.uk

Q. Can I set CF server variables?
A. Yes

Q. Can I have custom tags in a separate directory?
A. Yes

Q. Can I encrypt my code using the "cfcrypt" programme?
A. Yes

Q. What databases do you support?
A. We support MS Access and MS SQL database engines on the Windows2000/CF platform and MySQL database engine on the UNIX platform.

Q. What log files do you generate?
A. Our web servers are creating standard NCSA/IIS log files with referrer fields. We can also provide you with the log files on request or store them automatically on your web space.

Q. What is the (default) timeout on Session variables?
A. The default session variables timeout is 24h.

Q. Do you allow CFX tags such as "CFX_Encrypt" or "CFX_PGP" from the Allaire tag gallery?
A. We are flexible about registeringWell, so did I any custom CFX tags which is provided from the client side. However, usual procedure is that we first check CFX tag for possible security and performance implications on the hosting system platform.




Copyright © 1997-2010 DataGate. All rights reserved. Acceptable Uses Policy