[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date
][Minivend by thread
]
Re: [mv] Setting MV session ID from outside of Minivend.
****** message to minivend-users from Mike Heins <mikeh@minivend.com> ******
Quoting jojo@buchonline.net (jojo@buchonline.net):
> ****** message to minivend-users from jojo@buchonline.net ******
>
> On 7 Apr, Mike Heins wrote:
> > I am doing some work with mod_perl and Minivend. Some things
> > on the target list, in current expected order/likelihood
> > of implementation:
> >
> > -- coordinate with timed-build to deliver pages that
> > are pre-built, i.e. static pages. This would be
> > cookie-based, i.e. the catalog would mark a user
> > session to do caching on any of several levels:
> >
> > * when not logged in
> > * when logged in
> > * when items are not in basket
> > * when items are in basket
> > * user definable levels
> >
> > -- Routing of catalogs based on the invocation
> > SCRIPT_NAME and HTTP_HOST. This would mean
> > you can have one tlink program and run any
> > number of catalogs from it.
> >
> > -- Robot defense and throttling.
> >
> > -- Access logging / usertracking.
> >
> > -- preselection of search results via a SQL query
> > or other method, with those results passed to
> > Minivend for display.
> >
> > -- coordination for payment gateways that route
> > you to a third-party HTTP server
> >
> > I am still looking at features, so if anyone has any input it would
> > have an excellent chance of getting in the framework.
>
> Ummm...regarding Robots defense, do you add a feature to block a bad
> robots _and_ with no stopping or hunging the minivend server?
I have no idea what you are talking about. Of course the object is to not
have the MV server stop. I run about 50 different Minivend installations,
encompassing thousands of catalogs, and none of them stop or hang on
more than just the occasional (months or years between) basis. As
with all catalogs, they regularly get hit by the poorly-behaved robots
that claim to provide "offline viewing". If you put in a reasonable
robot defense using the standard facilities this should be the case.
If you are running BSD, you may see hangs, but that is not Minivend's
fault IMHO. It is their kernel interrupting socket reads where no other
OS does. This is true for any Perl program that uses sockets. The only
reason Minivend gets hit is that it is a long-running daemon process. Even
then, later versions of MV should eventually recover depending on what
you set HouseKeeping and PIDcheck to.
>
> Regarding "looking at features"...how about a special debug log, if
> something is going wrong? What i mean is, sometimes my minivend server
> is unavailable and no messages is in my error.log and i´m missing the
> minivend server via top, ps, sockstat, etc. Maybe there are any codes
> in minivend to kill minivend itselfs?
>
Again, I have little idea what you are talking about other than that we could
possibly put some STDERR messages saying something like "connection refused"
or somesuch.
Remember, this is Perl, so this type of thing can be made modular.
One thing that might make sense is to put a module in with somethink
like:
BEGIN {
require MV::UserDiagnostics;
$UserDiags = 1;
}
if($UserDiags) {
MV::UserDiagnostics::check_start();
}
.... main body of program ....
if($UserDiags) {
MV::UserDiagnostics::check_end();
}
Interfacing to outside programs could be left to those modules, for using
things like top and ps are outside the purview of something like this.
I encourage anyone to play with tlink.pl and mod_perl_tlink.pl and see
what can be done.
--
Internet Robotics, 131 Willow Lane, Floor 2, Oxford, OH 45056
phone +1.513.523.7621 fax 7501 <mikeh@minivend.com>
If you like what you're gettin', keep doin' what you're doin'. -- Hector
-
To unsubscribe from the list, DO NOT REPLY to this message. Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list
