view release on metacpan or search on metacpan
src/Source/LibWebP/src/utils/thread.h view on Meta::CPAN
// State of the worker thread object
typedef enum {
NOT_OK = 0, // object is unusable
OK, // ready to work
WORK // busy finishing the current task
} WebPWorkerStatus;
// Function to be called by the worker thread. Takes two opaque pointers as
// arguments (data1 and data2), and should return false in case of error.
typedef int (*WebPWorkerHook)(void*, void*);
view all matches for this distribution
view release on metacpan or search on metacpan
patches/Makefile_iup.mingw view on Meta::CPAN
CF_iupmatrixex = -c -Wall -O2 -Iinclude -Isrc -Isrcmatrixex -I../cd/include $(CF_iupmatrixex_EXTRA)
LF_iupmatrixex = -liup -liupcontrols -lcd -lfreetype6 -lzlib1 -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -luuid -loleaut32 -lole32 -lcomctl32 $(LF_iupmatrixex_EXTRA)
SLIB_iupmatrixex = ./lib/$(BUILDNICK)/libiupmatrixex.a
DLIB_iupmatrixex = ./lib/$(BUILDNICK)/libiupmatrixex.dll.a
ILIB_iupmatrixex = ./lib/$(BUILDNICK)/iupmatrixex_alien_.dll
OBJS_iupmatrixex = ./obj/$(BUILDNICK)/iupmatrixex/iup_matrixex.o ./obj/$(BUILDNICK)/iupmatrixex/iupmatex_clipboard.o ./obj/$(BUILDNICK)/iupmatrixex/iupmatex_busy.o ./obj/$(BUILDNICK)/iupmatrixex/iupmatex_export.o ./obj/$(BUILDNICK)/iupmatrixex/iupmat...
./obj/$(BUILDNICK)/iupmatrixex/iup_matrixex.o : srcmatrixex/iup_matrixex.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_clipboard.o : srcmatrixex/iupmatex_clipboard.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_busy.o : srcmatrixex/iupmatex_busy.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_export.o : srcmatrixex/iupmatex_export.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_visible.o : srcmatrixex/iupmatex_visible.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_copy.o : srcmatrixex/iupmatex_copy.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_units.o : srcmatrixex/iupmatex_units.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
./obj/$(BUILDNICK)/iupmatrixex/iupmatex_find.o : srcmatrixex/iupmatex_find.c ; gcc $(CF_ALL) $(CF_iupmatrixex) $^ -o $@
view all matches for this distribution
view release on metacpan or search on metacpan
src/judy-1.0.5/install-sh view on Meta::CPAN
# to itself, or perhaps because mv is so ancient that it does not
# support -f.
# Now remove or move aside any old file at destination location.
# We try this two ways since rm can't unlink itself on some
# systems and the destination file might be busy for other
# reasons. In this case, the final cleanup might fail but the new
# file should still install successfully.
{
if test -f "$dstdir/$dstfile"; then
$doit $rmcmd -f "$dstdir/$dstfile" 2>/dev/null \
view all matches for this distribution
view release on metacpan or search on metacpan
inc/inc_Archive-Extract/Archive/Extract.pm view on Meta::CPAN
local $IPC::Cmd::INSTANCES = 1;
($PROGRAMS->{$pgm}) = grep { ON_NETBSD ? m!/usr/pkg/! : m!/usr/local! } can_run($pgm);
next CMD;
}
if ( $pgm eq 'unzip' and ON_LINUX ) {
# Check if 'unzip' is busybox masquerading
local $IPC::Cmd::INSTANCES = 1;
my $opt = ON_VMS ? '"-Z"' : '-Z';
($PROGRAMS->{$pgm}) = grep { scalar run(command=> [ $_, $opt, '-1' ]) } can_run($pgm);
next CMD;
}
view all matches for this distribution
view release on metacpan or search on metacpan
corpus/autoheck-libpalindrome/install-sh view on Meta::CPAN
# to itself, or perhaps because mv is so ancient that it does not
# support -f.
{
# Now remove or move aside any old file at destination location.
# We try this two ways since rm can't unlink itself on some
# systems and the destination file might be busy for other
# reasons. In this case, the final cleanup might fail but the new
# file should still install successfully.
{
test ! -f "$dst" ||
$doit $rmcmd -f "$dst" 2>/dev/null ||
view all matches for this distribution
view release on metacpan or search on metacpan
patches/SDL_Pango-0.1.2-config-tools.3.patch view on Meta::CPAN
&& { test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } \
&& { test -z "$chmodcmd" || $doit $chmodcmd "$dsttmp"; } &&
- # Now remove or move aside any old file at destination location. We
- # try this two ways since rm can't unlink itself on some systems and
- # the destination file might be busy for other reasons. In this case,
- # the final cleanup might fail but the new file should still install
- # successfully.
- {
- if test -f "$dstdir/$dstfile"; then
- $doit $rmcmd -f "$dstdir/$dstfile" 2>/dev/null \
patches/SDL_Pango-0.1.2-config-tools.3.patch view on Meta::CPAN
+ # to itself, or perhaps because mv is so ancient that it does not
+ # support -f.
+
+ # Now remove or move aside any old file at destination location.
+ # We try this two ways since rm can't unlink itself on some
+ # systems and the destination file might be busy for other
+ # reasons. In this case, the final cleanup might fail but the new
+ # file should still install successfully.
+ {
+ if test -f "$dstdir/$dstfile"; then
+ $doit $rmcmd -f "$dstdir/$dstfile" 2>/dev/null \
view all matches for this distribution
view release on metacpan or search on metacpan
src/subversion/build/install-sh view on Meta::CPAN
# to itself, or perhaps because mv is so ancient that it does not
# support -f.
{
# Now remove or move aside any old file at destination location.
# We try this two ways since rm can't unlink itself on some
# systems and the destination file might be busy for other
# reasons. In this case, the final cleanup might fail but the new
# file should still install successfully.
{
test ! -f "$dst" ||
$doit $rmcmd -f "$dst" 2>/dev/null ||
view all matches for this distribution
view release on metacpan or search on metacpan
share/swagger-ui-bundle.js view on Meta::CPAN
*
* Copyright (c) Facebook, Inc. and its affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*/Object.defineProperty(t,"__esModule",{value:!0});var r="function"==typeof Symbol&&Symbol.for,o=r?Symbol.for("react.element"):60103,i=r?Symbol.for("react.portal"):60106,a=r?Symbol.for("react.fragment"):60107,s=r?Symbol.for("react.strict_mode"):6010...
/*!
* https://github.com/Starcounter-Jack/JSON-Patch
* (c) 2017 Joachim Wester
* MIT license
*/
view all matches for this distribution
view release on metacpan or search on metacpan
share/examples/ux/css/ux-all.css view on Meta::CPAN
height: 21px;
line-height: 21px;
padding: 0 4px;
*/
}
.x-statusbar .x-status-busy {
padding-left: 25px !important;
background: transparent no-repeat 3px 2px;
}
.x-toolbar div.xtb-text
share/examples/ux/css/ux-all.css view on Meta::CPAN
#word-status .x-status-text-panel .spacer {
width: 60px;
font-size:0;
line-height:0;
}
#word-status .x-status-busy {
padding-left: 25px !important;
background: transparent no-repeat 3px 2px;
}
#word-status .x-status-saved {
padding-left: 25px !important;
share/examples/ux/css/ux-all.css view on Meta::CPAN
/* *********************************************************** */
/* StatusBar - visual */
.x-statusbar .x-status-busy {
background-image: url(../images/loading.gif);
}
.x-statusbar .x-status-text-panel {
border-color: #99bbe8 #fff #fff #99bbe8;
}
share/examples/ux/css/ux-all.css view on Meta::CPAN
/* StatusBar word processor example styles */
#word-status .x-status-text {
color: #777;
}
#word-status .x-status-busy {
background-image: url(../images/saving.gif);
}
#word-status .x-status-saved {
background-image: url(../images/saved.png);
}
view all matches for this distribution
view release on metacpan or search on metacpan
xgboost/dmlc-core/doc/Doxyfile view on Meta::CPAN
# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
# determine which symbols to keep in memory and which to flush to disk.
# When the cache is full, less often used symbols will be written to disk.
# For small to medium size projects (<1000 input files) the default value is
# probably good enough. For larger projects a too small cache size can cause
# doxygen to be busy swapping symbols to and from disk most of the time
# causing a significant performance penalty.
# If the system has enough physical memory increasing the cache will improve the
# performance by keeping more symbols in memory. Note that the value works on
# a logarithmic scale so increasing the size by one will roughly double the
# memory usage. The cache size is given by this formula:
view all matches for this distribution
view release on metacpan or search on metacpan
libcares/ares_platform.c view on Meta::CPAN
{"smar-se-port1", {NULL}, 4987, "udp"},
{"smar-se-port2", {NULL}, 4988, "tcp"},
{"smar-se-port2", {NULL}, 4988, "udp"},
{"parallel", {NULL}, 4989, "tcp"},
{"parallel", {NULL}, 4989, "udp"},
{"busycal", {NULL}, 4990, "tcp"},
{"busycal", {NULL}, 4990, "udp"},
{"vrt", {NULL}, 4991, "tcp"},
{"vrt", {NULL}, 4991, "udp"},
{"hfcs-manager", {NULL}, 4999, "tcp"},
{"hfcs-manager", {NULL}, 4999, "udp"},
{"commplex-main", {NULL}, 5000, "tcp"},
view all matches for this distribution
view release on metacpan or search on metacpan
libuv/ChangeLog view on Meta::CPAN
* unix: remove overzealous assert (Ben Noordhuis)
* unix: clear UV_STREAM_SHUTTING after shutdown() (Ben Noordhuis)
* unix: fix busy loop, write if POLLERR or POLLHUP (Ben Noordhuis)
2013.06.05, Version 0.10.10 (Stable), 0d95a88bd35fce93863c57a460be613aea34d2c5
Changes since version 0.10.9:
view all matches for this distribution
view release on metacpan or search on metacpan
Amethyst/Brain/Infobot/Module/Excuse.pm view on Meta::CPAN
The UPS doesn't have a battery backup.
Recursivity. Call back if it happens again.
Someone thought The Big Red Button was a light switch.
The mainframe needs to rest. It's getting old, you know.
I'm not sure. Try calling the Internet's head office -- it's in the book.
The lines are all busy (busied out, that is -- why let them in to begin with?).
Jan 9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1
It's those computer people in X {city of world}. They keep stuffing things up.
A star wars satellite accidently blew up the WAN.
Fatal error right in front of screen
That function is not currently supported, but Bill Gates assures us it will be featured in the next upgrade.
Amethyst/Brain/Infobot/Module/Excuse.pm view on Meta::CPAN
Cow-tippers tipped a cow onto the server.
tachyon emissions overloading the system
Maintence window broken
We're out of slots on the server
Computer room being moved. Our systems are down for the weekend.
Sysadmins busy fighting SPAM.
Repeated reboots of the system failed to solve problem
Feature was not beta tested
Domain controler not responding
Someone else stole your IP address, call the Internet detectives!
It's not RFC-822 compliant.
Amethyst/Brain/Infobot/Module/Excuse.pm view on Meta::CPAN
Hash table has woodworm
Trojan horse ran out of hay
Zombie processess detected, machine is haunted.
overflow error in /dev/null
Browser's cookie is corrupted -- someone's been nibbling on it.
Mailer-daemon is busy burning your message in hell.
According to Microsoft, it's by design
vi needs to be upgraded to vii
greenpeace free'd the mallocs
Terorists crashed an airplane into the server room, have to remove /bin/laden. (rm -rf /bin/laden)
astropneumatic oscillations in the water-cooling
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Any/Daemon.pm view on Meta::CPAN
BIRTH:
while(keys %childs < $max_childs)
{ my $kid = fork;
unless(defined $kid)
{ alert "cannot fork new children" unless $silence_warn++;
sleep 1; # wow, back down! Probably too busy.
$silence_warn = 0 if $silence_warn==SLOW_WARN_AGAIN_AFTER;
next BIRTH;
}
if($kid==0)
view all matches for this distribution
view release on metacpan or search on metacpan
=item load => $count (default: 2)
The maximum number of concurrent jobs sent to a single worker process.
Jobs that cannot be sent to a worker immediately (because all workers are
busy) will be queued until a worker is available.
Setting this low improves latency. For example, at C<1>, every job that
is sent to a worker is sent to a completely idle worker that doesn't run
any other jobs. The downside is that throughput is reduced - a worker that
finishes a job needs to wait for a new job from the parent.
The default of C<2> is usually a good compromise.
=item start => $seconds (default: 0.1)
When there are fewer than C<idle> workers (or all workers are completely
busy), then a timer is started. If the timer elapses and there are still
jobs that cannot be queued to a worker, a new worker is started.
This sets the minimum time that all workers must be busy before a new
worker is started. Or, put differently, the minimum delay between starting
new workers.
The delay is small by default, which means new workers will be started
relatively quickly. A delay of C<0> is possible, and ensures that the pool
my $proc = $pool[0];
if ($proc->[0] < $load) {
# found free worker, increase load
unless ($proc->[0]++) {
# worker became busy
--$nidle
or undef $stop_w;
$want_start->()
if $nidle < $idle && @pool < $max;
my $job = shift @queue;
my $ocb = pop @$job;
$proc->[2]->(@$job, sub {
# reduce load
--$proc->[0] # worker still busy?
or ++$nidle > $idle # not too many idle processes?
or $want_stop->();
Array::Heap::adjust_heap_idx @pool, $proc->[1]
if defined $proc->[1];
pool size to the number of cpus in your system, and C<load> to at least
C<2>, to make sure there can be another job waiting for the worker when it
has finished one.
The value of C<2> for C<load> is the minimum value that I<can> achieve
100% throughput, but if your parent process itself is sometimes busy, you
might need higher values. Also there is a limit on the amount of data that
can be "in flight" to the worker, so if you send big blobs of data to your
worker, C<load> might have much less of an effect.
=item high throughput, I/O bound jobs - set load >= 2, max = 1, or very high
view all matches for this distribution
view release on metacpan or search on metacpan
requests.
It also shows how to embed the actual child code into a C<__DATA__>
section, so it doesn't need any external files at all.
And when your parent process is often busy, and you have stricter timing
requirements, then running timers in a child process suddenly doesn't look
so silly anymore.
Without further ado, here is the code:
While the overall ordering isn't guaranteed, the async backend still
guarantees that events and responses are delivered to the parent process
in the exact same ordering as they were generated in the child process.
And unless your system is I<very> busy, it should clearly show that the
job started last will finish first, as it has the lowest count.
This concludes the async example. Since L<AnyEvent::Fork> does not
actually fork, you are free to use about any module in the child, not just
L<AnyEvent>, but also L<IO::AIO>, or L<Tk> for example.
The synchronous backend also has no overhead due to running an event loop
- reading requests is therefore very efficient, while writing responses is
less so, as every response results in a write syscall.
If the parent process is busy and a bit slow reading responses, the child
waits instead of processing further requests. This also limits the amount
of memory needed for buffering, as never more than one response has to be
buffered.
The API in the child is simple - you just have to define a function that
It batches requests and responses reasonably efficiently, doing only as
few reads and writes as needed, but needs to poll for events via the event
loop.
Responses are queued when the parent process is busy. This means the child
can continue to execute any queued requests. It also means that a child
might queue a lot of responses in memory when it generates them and the
parent process is slow accepting them.
The API is not a straightforward RPC pattern - you have to call a
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/Gearman/WorkerPool.pm view on Meta::CPAN
my $workload = thaw($job->workload);
if( $workload ){
my $status = $workload->{status};
my ($key,$idx) = split(/__/,$workload->{channel});
DEBUG "SB $status $key $idx";
if( $status eq 'busy'){
$self->slots($key)->[$idx]->is_busy(1);
}
elsif( $status eq 'idle'){
$self->slots($key)->[$idx]->is_busy(0);
}
}
$job->complete;
} );
push(@reporters, $w);
lib/AnyEvent/Gearman/WorkerPool.pm view on Meta::CPAN
max=>3, # max workers
},
slots=>{
'TestWorker'=>{ # module package name which extends AnyEvent::Gearman::WorkerPool::Worker.
min=>20, # min workers, count when started.
max=>50, # overrides global config's max. Workers will extend when all workers are busy.
workleft=>10, # workleft is life of worker. A worker will be respawned after used 10 times.
# if workleft is set as 0, a worker will be never respawned.
# this feature is useful if worker code may has some memory leaks.
},
# you can place more worker modules here.
view all matches for this distribution
view release on metacpan or search on metacpan
Revision history for AnyEvent-Handle-ZeroMQ
0.09 2011.9.4
Fix a bug occured when busy on both reading and writing.
0.08 2011.7.23
Documented more.
0.07 2011.7.23
view all matches for this distribution
view release on metacpan or search on metacpan
MP/Transport.pm view on Meta::CPAN
=head2 MONITORING
Monitoring the connection itself is transport-specific. For TCP, all
connection monitoring is currently left to TCP retransmit time-outs
on a busy link, and TCP keepalive (which should be enabled) for idle
connections.
This is not sufficient for listener-less nodes, however: they need
to regularly send data (30 seconds, or the monitoring interval, is
recommended), so TCP actively probes.
view all matches for this distribution
view release on metacpan or search on metacpan
t/author-simple.t view on Meta::CPAN
## Test cases
my @cases = (
['default_values' => {high => .95, low => .80}],
['keep_it_busy' => {high => .97, low => .95}],
['take_it_slow' => {high => .30, low => .20}],
['high_and_low' => {high => .90, low => .10}],
[ 'half-empty' => {
high => .55,
low => .45,
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/Pg.pm view on Meta::CPAN
$self->_maybe_callback(on_notify => @notify);
}
if (defined (my $cq = $self->{current_query})) {
while (1) {
if ($self->{write_watcher} or $dbc->busy) {
$debug and $debug & 1 and $self->_debug($self->{write_watcher}
? "wants to write and read"
: "wants to read");
$self->{timeout_watcher} = AE::timer $self->{timeout}, 0, weak_method_callback_cached($self, '_on_timeout')
if $self->{timeout};
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/Redis/RipeRedis.pm view on Meta::CPAN
No matching script. Use the C<EVAL> command.
=item E_BUSY
Redis is busy running a script. You can only call C<SCRIPT KILL>
or C<SHUTDOWN NOSAVE>.
=item E_MASTER_DOWN
Link with MASTER is down and slave-serve-stale-data is set to 'no'.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/RipeRedis.pm view on Meta::CPAN
No matching script. Use the C<EVAL> command.
=item E_BUSY
Redis is busy running a script. You can only call C<SCRIPT KILL>
or C<SHUTDOWN NOSAVE>.
=item E_NOT_BUSY
No scripts in execution right now.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/Task.pm view on Meta::CPAN
=head1 STARTING THE SERVER
Typically you will want to start the client and server as completely separate processes as shown in the synopses.
Running the server and the client in the same process is technically possible but is highly discouraged since the server will C<fork()> when the client demands a new worker process. In this case, all descriptors in use by the client are duped into th...
Since it's more of a bother than it's worth to run the server and the client in the same process, there is an alternate server constructor, C<AnyEvent::Task::Server::fork_task_server> for when you'd like to fork a dedicated server process. It can be ...
## my ($keepalive_pipe, $server_pid) =
AnyEvent::Task::Server::fork_task_server(
view all matches for this distribution
view release on metacpan or search on metacpan
t/06_pool.t view on Meta::CPAN
my $cv = condvar AnyEvent;
my $pool = pool qw( a b );
my $order = 0;
my @res;
my $busy = 0;
my $cnt = 1;
my $idle;
$idle = AE::idle sub {
$pool->get(sub {
my ($guard, $object) = @_;
$busy++;
push @res, { b => $busy, t => time };
my $timer;
$timer = AE::timer 0.1, 0 => sub {
$busy--;
undef $timer;
undef $guard;
if (@res >= 40) {
undef $idle;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/Worker/Pool.pm view on Meta::CPAN
$workers->do( @common_worker_do_args );
# Will be run instantly (left 0 idle workers)
$workers->do( @common_worker_do_args );
# Will be run after one of busy worker will get free
$workers->do( @common_worker_do_args );
$workers->take_worker(sub {
my $worker = shift;
$worker->do(@args, sub {
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent/XMPP.pm view on Meta::CPAN
=back
And yes, all these are essential for XMPP communication. Even though 'instant
messaging' and 'presence' is a quite simple problem XMPP somehow was successful
at making the task complicated enough to keep me busy for a long time. But all
of that time wasn't only for the technology required to get it started, mostly
it was for all the quirks, hacks and badly applied "XML" in the protocol which
complicated the matter.
=head1 RELEASE NOTES
lib/AnyEvent/XMPP.pm view on Meta::CPAN
Robin Redeker, C<< <elmex at ta-sa.org> >>, JID: C<< <elmex at jabber.org> >>
=head1 BUGS
Please note that I'm currently (July 2007) the only developer on this project
and I'm very busy with my studies in Computer Science. If you want to ease my
workload or want timely releases, please send me patches instead of bug reports
or feature requests. I won't forget the reports or requests if you can't or
didn't send patches, but I can't gurantee immediate response. But I will of
course try to fix/implement them as soon as possible!
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AnyEvent.pm view on Meta::CPAN
understand why). Callback invocation also has a high overhead compared to
the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
uses select or poll in basically all documented configurations.
Glib is hit hard by its quadratic behaviour w.r.t. many watchers. It
clearly fails to perform with many filehandles or in busy servers.
POE is still completely out of the picture, taking over 1000 times as long
as EV, and over 100 times as long as the Perl implementation, even though
it uses a C-based event loop in this case.
view all matches for this distribution
view release on metacpan or search on metacpan
A web application starts when the user visits a page in that
application, and has a new $Session created. Right before
the first $Session is created, the $Application is created.
When the last user $Session expires, that $Application
expires also. For some web applications that are always busy,
the Application_OnEnd event may never occur.
=head2 Script_OnStart & Script_OnEnd
The script events are used to run any code for all scripts
performs session cleanup. The timing of the Session_OnEnd does not
occur immediately after the session times out, but when the first
script runs after the session expires, and the StateManager allows
for that session to be cleaned up.
So on a busy site with default SessionTimeout (20 minutes) and
StateManager (10 times) settings, the Session_OnEnd for a particular
session should be run near 22 minutes past the last activity that Session saw.
A site infrequently visited will only have the Session_OnEnd run
when a subsequent visit occurs, and theoretically the last session
of an application ever run will never have its Session_OnEnd run.
As of version 2.23 this value is updated correctly
before global.asa Script_OnStart is called, so
global script termination may be correctly handled
during that event, which one might want to do
with excessive user STOP/RELOADS when the web
server is very busy.
An API extension $Response->IsClientConnected
may be called for refreshed connection status
without calling first a $Response->Flush
global.asa's Script_OnStart.
=head2 Low MaxClients
Set your MaxClients low, such that if you have that
many httpd servers running, which will happen on busy site,
your system will not start swapping to disk because of
excessive RAM usage. Typical settings are less than 100
even with 1 gig RAM! To handle more client connections,
look into a dual server, mod_proxy front end.
that get in there? Oh right, testing on Win32. :(
Very painful lesson this one, sorry to whom it may concern.
+$Application->SessionCount support turned off by default
must enable with SessionCount config option. This feature
puts an unnecessary load on busy sites, so not default
behavior now.
++XMLSubsMatch setting that allows the developer to
create custom tags XML style that execute perl subroutines.
See ./site/eg/xml_subs.asp
view all matches for this distribution