|
|
Interchange 5.7.1 (Development branch)
11-14-2008
Interchange is an advanced e-commerce platform. It enables you to build completely customized and flexible online shops, while utilizing the knowledge gathered in more than a decade of active development. It offers high level e-commerce functions, support for PostgreSQL, MySQL, and Oracle, templating, a complete shopping cart functionality, payment processing, inventory, tax and shipping calculation, discounts, Web-based administration, localization, event routing, SOAP-based RPC, a custom tag language, and the full power of Perl.License: GNU General Public License v2Changes:|
|
IC_MOD_PERL(1p) User Contributed Perl Documentation IC_MOD_PERL(1p) NAME
ic_mod_perl -- Run Interchange entirely inside Apache/mod_perl SYNOPSIS
# Add to Apache httpd.conf: PerlRequire /usr/lib/interchange/bin/ic_mod_perl PerlChildInitHandler Vend::ModPerl::child_start PerlChildExitHandler Vend::ModPerl::child_end <Location /ic> SetHandler perl-script PerlHandler Vend::ModPerl PerlSendHeader Off PerlSetupEnv On </Location> DESCRIPTION
Benefits o Possibly better stability, especially on non-Linux platforms where Perl signals are often buggy. o Use less memory total; don't have preforked Apache and Interchange daemons. Adds about 8 MB more to a typical Apache/mod_perl child process, for a total of, say, 32 MB per Apache child process. But standalone Interchange usually has 3 processes: an Interchange child process (~24 MB), an httpd child (~24 MB), and a link CGI (~1 MB), so it's actually a decent savings in total memory used. o Speed (ranging from slightly faster to the same on heavy pages, to 10 hits/sec. faster on empty pages). o Debugging -- delve into bowels with Apache::Status. o Easier coexistence with other mod_perl code and libraries. o Can coexist with standalone Interchange codebase without problems. o Administrative ease (for sysadmins who know Apache but not Interchange). Drawbacks o Interchange runs as web server user, which in a standard system is usually apache or www, so you wouldn't want to share that Apache installation with untrusted user CGIs, PHP, etc. as they could read any Interchange files, including DSNs, userdb, etc. o Apache needs to be dedicated, or very closely watched because all mod_perl stuff runs in the same interpreter, and lots of mod_perl code doesn't use Safe. o How do you scale to multiple app servers in this configuration? o Hardware or software port redirector o Tux CGI front-end redirector like tlink o Separate lightweight Apache (no modules) that proxies /ic requests Ideal system setup Use Tux to serve images & static content, and a dedicated Apache for Interchange running under the 'interch' user and with no UserDir, CGI, PHP, etc. enabled and an empty DocRoot. CAVEATS
o Watch out for differing Storable versions in sessions when switching between standalone and mod_perl runs! BUGS
o Haven't yet implemented form/multipart submissions. o Don't yet handle TolerateGet. o Don't yet handle MiniVend 3 style GETs (mv_session_id;mv_arg;mv_pc) o URIs must follow format "/ic/catalogname/page...", where /ic is customizable but must only be one "directory" deep (i.e., no slashes). AUTHOR
Jon Jensen <jon@icdevgroup.org>, March 2002 perl v5.14.2 2012-01-23 IC_MOD_PERL(1p)