03-18-2005
I'm not an expert user on frontpage but I'm not really sure microsoft products work really well with apache or unix/ linux products in general. And as for using php/ perl tags, these are not tag-based languages. Coldfusion is. Maybe it is better to set this up on a Windows platform with IIS/ SQL server or access or even MySQL for windows.
The most common layouts for webservers with scripting or programming languages are:
1/ apache/ php/ perl/ mysql on linux or unix
2/ apache/ tomcat/ j2ee/ oracle (or whatever database) on linux or unix
3/ IIS/ ASP/ SQL server on windows
4/ IIS/ Coldfusion/ SQL server on windows
I think frontpage would fall under number 3.
3 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
my company is considering a new development of our web site, which used to run on Apachi over Solaris.
The company who is going to do this for us knows only about developing it in ASP.
I guess this means we'll have to have another ISS server on NT for these dynamic pages :(
What are... (5 Replies)
Discussion started by: me2unix
5 Replies
2. UNIX for Dummies Questions & Answers
Hi there all
I am looking for both a web browser as well as a web server (Ie. Netscape Fasttrack) that will run on HPUX 10.
If you know where I can get these free via FTP, please contact me as soon as possible!!
Thanks,
Mark (1 Reply)
Discussion started by: mleathers
1 Replies
3. Solaris
Java web console Vs Web-Based Enterprise Management(WBEM)
1. I like to understand the difference in purpose of using java web console and Web-Based Enterprise Management (WBEM)
2. As per CIS benchmark, both of them has to be disabled when not used for increased security.
Solaris admin(s) -... (0 Replies)
Discussion started by: cyberidude
0 Replies
LEARN ABOUT DEBIAN
jifty::web::session::none
Jifty::Web::Session::None(3pm) User Contributed Perl Documentation Jifty::Web::Session::None(3pm)
NAME
Jifty::Web::Session::None - A null session handler for jifty
DESCRIPTION
Jifty depends on its sessions to keep users logged in, to store continuations and to allow developers to store user-specific data. In
general, you don't want to disable them. But sometimes, the development benefits of Jifty lead you to build applications that genuinely
don't want per-user sessions. That's where "Jifty::Web::Session::None" comes in. By specifying that you want to use
"Jifty::Web::Session::None" as your Jifty session handler, you tell Jifty to avoid ever reading, writing or storing a user session. No
cookies get set. Nothing gets stored in the database.
USAGE
In your "etc/config.yml":
---
framework:
Web:
SessionClass:: Jifty::Web::Session::None
METHODS
All methods in this class are dummy methods which do no work. This class mocks the API provided by "Jifty::Web::Session".
new
Takes no arguments. Returns a Jifty::Web::Session::None.
id
Returns false.
create
Returns true.
load
Returns true.
unload
Returns true.
loaded
Returns true.
get
Returns false.
set
Returns false.
remove
Returns true.
set_continuation
Returns false.
get_continuation
Returns false.
remove_continuation
Returns false.
continuations
Returns false.
set_cookie
Returns false.
cookie_name
Returns false.
expires
Returns false.
perl v5.14.2 2010-09-25 Jifty::Web::Session::None(3pm)