The Net::Amazon::AWIS module allows you to use the Amazon Alexa Web
Information Service.
The Alexa Web Information Service (AWIS) provides developers with
programmatic access to the information Alexa Internet (www.alexa.com)
collects from its Web Crawl, which currently encompasses more than 100
terabytes of data from over 4 billion Web pages. Developers and Web
site owners can use AWIS as a platform for finding answers to
difficult and interesting problems on the Web, and incorporating them
into their Web applications.
In order to access the Alexa Web Information Service, you will need an
Amazon Web Services Subscription ID. See
http://www.amazon.com/gp/aws/landing.html
Registered developers have free access to the Alexa Web Information
Service during its beta period, but it is limited to 10,000 requests
per subscription ID per day.
There are some limitations, so be sure to read The Amazon Alexa
Web Information Service FAQ.
Beaker is built on code from the package MyghtyUtils, originally used
in the Myghty project. It implements a full set of cache functionality
along with sessions that can utilize the caches.
Beaker includes Cache and Session WSGI middleware to ease integration
with WSGI capable frameworks, and is automatically used by Pylons.
Features
* Fast, robust performance
* Multiple reader/single writer lock system to avoid duplicate
simultaneous cache creation
* Cache back-ends include dbm, file, memory, memcached, and
database (Using SQLAlchemy for multiple-db vendor support)
* Signed cookie's to prevent session hijacking/spoofing
* Extensible Container object to support new back-ends
* Cache's can be divided into namespaces (to represent templates,
objects, etc.) then keyed for different copies
* Create functions for automatic call-backs to create new cache
copies after expiration
* Fine-grained toggling of back-ends, keys, and expiration per
Cache object
This is a django application that tries to eliminate annoying
things in the Django framework.
Features:
render_to decorator - reduce typing in django views.
signals decorator - allow use signals as decorators.
ajax_request decorator - returns JsonResponse with this dict as content.
autostrip decorator - strip text form fields before validation.
get_object_or_None function - similar to get_object_or_404, but
returns None if object not found.
get_config function - get settings from django.conf if exists,
return default value otherwise.
AutoOneToOne field - creates related object on first call if it
doesn't exist yet.
HttpResponseReload - reload and stay on same page from where request
was made.
StaticServer middleware - instead of configuring urls.py, just
add this middleware and it will serve you static files.
JSONField - custom field that lets you easily store JSON data in one of
your model fields.
Building upon Crash Recovery, this extension allows you to save the
current state of Firefox (history, text data, cookies) and return
to that state at any later moment. Besides the manually saved states,
Session Manager automatically stores the current state in case of a
crash.
All sessions are stored in the "sessions" folder inside your profile
directory and can be moved around as any other file. To get to that
folder, simply select "Open Session Folder" in Session Manager's menu
(might not work on all OSes). Finally, Session Manager also allows to
reopen the 10 last closed windows and tabs.
It is not recommended to use Session Manager at the same time as Crash
Recovery (which is completely integrated), SessionSaver or Tab Mix Plus
(which provide similar functionality on their own). In comparison,
Session Manager currently stores more session data than Tab Mix Plus
while not getting as complex as SessionSaver.
A next generation web framework for the Perl programming language; duct
tape for the HTML5 web.
An amazing real-time web framework, allowing you to easily grow single file
prototypes into well-structured web applications.
Powerful out of the box with RESTful routes, plugins, commands, Perl-ish
templates, content negotiation, session management, form validation, testing
framework, static file server, CGI/PSGI detection, first class Unicode support
and much more for you to discover.
Full stack HTTP and WebSocket client/server implementation with IPv6, TLS, SNI,
IDNA, HTTP/SOCKS5 proxy, Comet (long polling), keep-alive, connection pooling,
timeout, cookie, multipart and gzip compression support.
Built-in non-blocking I/O web server, supporting multiple event loops as well
as optional preforking and hot deployment, perfect for building highly scalable
web services.
JSON and HTML/XML parser with CSS selector support.
The WebStone benchmark tests were originally developed by Silicon Graphics
to measure the performance of Web server software and hardware products.
WebStone 2.0.1 is a more portable version of the original WebStone
benchmark which added support to use Windows NT systems as client test
systems.
Mindcraft, Inc. has acquired the rights to WebStone from Silicon Graphics.
WebStone 2.5 is Mindcraft's enhancement to WebStone 2.0.1 to improve
reliability and portability as well as to make tests more reproducible.
WebStone 2.5 also offers new workloads for CGI and API tests (see below
for more details). WebStone 2.5 provides performance-identical test
results with WebStone 2.0.1 when using the same workloads
This FreeBSD port rely on rsh and rcp being allowed for the user proces
running webstone between the web server and web clients. This is not
enable per default in FreeBSD, and root is never allowed to do it without
entering password for each operation.
This package contains the set of ukrainian fonts for X11 Release 6.
Copyright (C) 1995 Victor Forsyuk <victor@gu.net>
This set is based on so-called "Cronyx" font set, that was copyrighted
by Cronyx Ltd.: Copyright (C) 1994-1995 Cronyx Ltd.
Under no circumstances is the author responsible for the proper
functioning of this software, nor does the author assume any
responsibility for damages incurred with its use.
This port also creates two aliases for each of the fonts -- for koi8-r
encoding (koi8-u is a superset of koi8-r anyway) and for cronyx foundry.
Some applications (gtk?) look for -cronyx-*- and/or *-koi8-r explicitly,
but there is no reason why this fonts can not be used in those cases.
This is a little hack I wrote to help in setting up new Type 1 PostScript
fonts for use with X. It automatically constructs the fonts.scale file which
X uses to identify fonts in can use the current directory. Previously you
had to write this file by hand which is unacceptable if you have lots of
fonts.
The program can also generate Fontmap entries for Ghostscript (which can
then be put in the global Fontmap to speed up startup times) and it can
produce font sample sheets as well.
Please be warned that this is beta quality software and has limitations. I
think you will, however, find it useful and the bugs will go away over time
if people help me with it.
Reports of success or otherwise welcomed at the address below.
----------------------------------------------------------------------------
James Macnicol (J.Macnicol@student.anu.edu.au)
The proggy programmer's fonts (Proggy Clean, Proggy Square, Proggy Small,
and Proggy Tiny) are a set of fixed-width screen fonts that are designed
for code listings. Each font only comes in one size that it looks good at.
The fonts were optimized while coding in C or C++. For this reason,
characters like the '*' were placed vertically centered, as '*' usually
means dereference or multiply, but never 'to the power of' like in Fortran.
The {}s are centered horizontally (as the author's coding style aligns
braces vertically), the zero looks different from the capital oh, and there
is never any confusion between ells, ones, and eyes. Additionally, the
arithmetic operators (+ - * < >) are all axis aligned.
The proggy programmer's fonts (Proggy Clean, Proggy Square, Proggy Small,
and Proggy Tiny) are a set of fixed-width screen fonts that are designed
for code listings. Each font only comes in one size that it looks good at.
The fonts were optimized while coding in C or C++. For this reason,
characters like the '*' were placed vertically centered, as '*' usually
means dereference or multiply, but never 'to the power of' like in Fortran.
The {}s are centered horizontally (as the author's coding style aligns
braces vertically), the zero looks different from the capital oh, and there
is never any confusion between ells, ones, and eyes. Additionally, the
arithmetic operators (+ - * < >) are all axis aligned.