store owners
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2086
Email::Store 0.24
Email::Store is a framework for database-backed email storage. more>>
Email::Store is a framework for database-backed email storage.
SYNOPSIS
use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once
Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );
...
Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.
Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
<<lessSYNOPSIS
use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once
Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );
...
Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.
Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
Download (0.027MB)
Added: 2006-06-28 License: Perl Artistic License Price:
1215 downloads
Google Gears Beta
Google Gears project is an open source Firefox extension that enables web applications to provide offline functionality. more>>
Google Gears project is an open source Firefox extension that enables web applications to provide offline functionality using following JavaScript APIs:
- Store and serve application resources locally
- Store data locally in a fully-searchable relational database
- Run asynchronous Javascript to improve application responsiveness
<<less- Store and serve application resources locally
- Store data locally in a fully-searchable relational database
- Run asynchronous Javascript to improve application responsiveness
Download (0.42MB)
Added: 2007-06-01 License: Freeware Price:
1030 downloads
Apache-Storage 1.00
Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process. more>>
Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.
<<less Download (0.004MB)
Added: 2005-08-24 License: GPL (GNU General Public License) Price:
1521 downloads
Class::DataStore 0.07
Class::DataStore is a Perl module for generic OO data storage/retrieval. more>>
Class::DataStore is a Perl module for generic OO data storage/retrieval.
SYNOPSIS
my %values = ( one => 1, two => 2 );
my $store = Class::DataStore->new( %values );
# using get/set methods
$store->set( three, 3 );
my $three = $store->get( three );
# using AUTOLOAD method
$store->four( 4 );
my $four = $store->four;
my @four = $store->four; # returns a list
my $exists = $store->exists( three ); # $exists = 1
my $data_hashref = $store->dump;
$store->clear;
Class::DataStore implements a simple storage system for object data. This data can be accessed via get/set methods and AUTOLOAD. AUTOLOAD calls are not added to the symbol table, so using get/set will be faster. Using AUTOLOAD also means that you will not be able to store data with a key that is already used by a instance method, such as "get" or "exists".
This module was written originally as part of a website framework that was used for the Democratic National Committee website in 2004. Some of the implementations here, such as get() optionally returning a list if called in array context, reflect the way this module was originally used for building web applications.
Class::DataStore is most useful when subclassed. To preserve the AUTOLOAD functionality, be sure to add the following when setting up the subclass:
use base Class::DataStore;
*AUTOLOAD = &Class::DataStore::AUTOLOAD;
This module is also a useful add-on for modules that need quick and simple data storage, e.g. to store configuration data:
$self->{_config} = Class::Datastore->new( $config_data );
sub config { return $_[0]->{_config}; }
my $server = $self->config->server;
my $sender = $self->config->get( sender );
<<lessSYNOPSIS
my %values = ( one => 1, two => 2 );
my $store = Class::DataStore->new( %values );
# using get/set methods
$store->set( three, 3 );
my $three = $store->get( three );
# using AUTOLOAD method
$store->four( 4 );
my $four = $store->four;
my @four = $store->four; # returns a list
my $exists = $store->exists( three ); # $exists = 1
my $data_hashref = $store->dump;
$store->clear;
Class::DataStore implements a simple storage system for object data. This data can be accessed via get/set methods and AUTOLOAD. AUTOLOAD calls are not added to the symbol table, so using get/set will be faster. Using AUTOLOAD also means that you will not be able to store data with a key that is already used by a instance method, such as "get" or "exists".
This module was written originally as part of a website framework that was used for the Democratic National Committee website in 2004. Some of the implementations here, such as get() optionally returning a list if called in array context, reflect the way this module was originally used for building web applications.
Class::DataStore is most useful when subclassed. To preserve the AUTOLOAD functionality, be sure to add the following when setting up the subclass:
use base Class::DataStore;
*AUTOLOAD = &Class::DataStore::AUTOLOAD;
This module is also a useful add-on for modules that need quick and simple data storage, e.g. to store configuration data:
$self->{_config} = Class::Datastore->new( $config_data );
sub config { return $_[0]->{_config}; }
my $server = $self->config->server;
my $sender = $self->config->get( sender );
Download (0.004MB)
Added: 2006-10-06 License: Perl Artistic License Price:
1113 downloads
G-Share 1.5 Beta
G-Share is a PHP script that allows you to share your Gmail attachments with the world. more>>
G-Share is a PHP script that allows you to share your Gmail attachments with the world, it is a download center with files stored in your gmail account.
G-Share project uses a MySQL database to store important data such as categories, download count, visitors, gmail accounts, etc...
<<lessG-Share project uses a MySQL database to store important data such as categories, download count, visitors, gmail accounts, etc...
Download (0.10MB)
Added: 2006-03-09 License: GPL (GNU General Public License) Price:
1324 downloads
eeStock 4.0
eeStock project is a Web application for managing an inventory. more>>
eeStock project is a Web application for managing an inventory.
eeStock is a free software which allows you to manage your stocks (items).
Its written in PHP4 and uses a PostgreSQL or MySQL database to store data.
Its divided in 2 sections:
- a user section
- an administration section
In the Stock managing section, users can:
.browse items by manufacturer, category, owner or location
.search items using a keyword
.borrow an item if this one is free
.return their items
.access to their profile
In the Administration section you can (if you have administrator or superuser rights):
.create, modify, duplicate, delete items
.browse all items (list)
.create, modify, delete categories (each category can have a parent category)
.create, modify, delete locations (each location can have a parent location)
.create, modify, delete manufacturers
.create, modify, delete users who will be owners of item(s) (only superusers)
System requirements:
- Apache (required)
- PHP (required)
- MySQL (optional)
- PostgreSQL (optional)
Install database
Create the eestock database (MySQL root user password required)
$ mysqladmin -h localhost -u root -p create eestock
Create the user "eestock" (MySQL root user password required)
$ mysql -h localhost -u root -D mysql -p < admin/utils/mysql/create_user.mysql
Create tables (MySQL root user password required)
$ mysql -h localhost -u root -D eestock -p < admin/utils/mysql/init_db.mysql
Edit file admin/config.inc to change the eestock user password.
<<lesseeStock is a free software which allows you to manage your stocks (items).
Its written in PHP4 and uses a PostgreSQL or MySQL database to store data.
Its divided in 2 sections:
- a user section
- an administration section
In the Stock managing section, users can:
.browse items by manufacturer, category, owner or location
.search items using a keyword
.borrow an item if this one is free
.return their items
.access to their profile
In the Administration section you can (if you have administrator or superuser rights):
.create, modify, duplicate, delete items
.browse all items (list)
.create, modify, delete categories (each category can have a parent category)
.create, modify, delete locations (each location can have a parent location)
.create, modify, delete manufacturers
.create, modify, delete users who will be owners of item(s) (only superusers)
System requirements:
- Apache (required)
- PHP (required)
- MySQL (optional)
- PostgreSQL (optional)
Install database
Create the eestock database (MySQL root user password required)
$ mysqladmin -h localhost -u root -p create eestock
Create the user "eestock" (MySQL root user password required)
$ mysql -h localhost -u root -D mysql -p < admin/utils/mysql/create_user.mysql
Create tables (MySQL root user password required)
$ mysql -h localhost -u root -D eestock -p < admin/utils/mysql/init_db.mysql
Edit file admin/config.inc to change the eestock user password.
Download (0.043MB)
Added: 2007-02-16 License: GPL (GNU General Public License) Price:
980 downloads
TeamPlanner 0.1.0
TeamPlanner is an organization application that allows the user to store events for several people which can be grouped in teams more>>
TeamPlanner is an organization application that allows the user to store events for several people which can be grouped in teams.
Events are organized into categories. The planning can be displayed and printed for any combination of teams, categories and people.
<<lessEvents are organized into categories. The planning can be displayed and printed for any combination of teams, categories and people.
Download (0.14MB)
Added: 2006-03-13 License: CeCILL (CeCILL Free Software License Agreement) Price:
1324 downloads
Email::Store::DBI 0.254
Email::Store::DBI is a Perl module for database backend to Email::Store. more>>
Email::Store::DBI is a Perl module for database backend to Email::Store.
SYNOPSIS
use Email::Store dbi:...;
This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.
"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.
Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
<<lessSYNOPSIS
use Email::Store dbi:...;
This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.
"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.
"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.
Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.
For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.
Download (0.028MB)
Added: 2006-10-03 License: Perl Artistic License Price:
1117 downloads
Support Incident Tracker 3.24
Support Incident Tracker (or SiT!) is a Web-based application for tracking technical support calls or emails. more>>
Support Incident Tracker (or SiT!) is a Web-based application for tracking technical support calls or emails.
Support Incident Tracker project can manage contacts, sites, technical support contracts, and support incidents in one place. You can send and receive email directly from SiT!, attaching files and recording every communication in the incident log.
SiT! is aware of Service Level Agreements, and incidents are flagged if they stray outside of them.
Support Incident Tracker grew out of an application developed by Salford Software since 2000 called Webtrack and is used in-house by Support Engineers to easily track support incidents.
Enhancements:
- Fixed service levels for reopened incidents, service level target opened is now added making the next action initial response
- Fixed regression where mark for closure was ignored and the incident was closed immediately
- Lists number of incidents of each priority a user has on the user listings page.
- Show more accurately who last updated the call on list incidents pages
- Added multiple global signatures, one is choosen at random when email is sent.
- Fixed bug where disabled user accounts would still display as having relevant skills
- Fixed issue where URLs would not be shortened if they contained a % (percent) or $ (dollar) symbol
- Fixed issues with URLs that contain colons
- Incidents page informs you more accuratly who updated the call
- Specified MySQL Engine type to be MyISAM on all table creations
- Call opening notes are shown in tool tip after new incidents logged rather than reassign
- BB Code. Basic set of BB codes supported in incident updates
- Prevent summary and solution from being uncheck from close incident page since these are mandatory
- Fixed bug with not sending closing email
- send_template_email now store emails in the incident log
- Holiday calendar is now functional
- New holiday planner shows when all users are in/out
- Users can now be placed in groups, view users shows just your own group by default
- Users with edit user permission can set users holiday entitlement
- Able to change external escalation details on bulk
- View users now has links to Waiting queues and holiday calendars
- New interface for adding vendors
- Ability to request email notification when a call is reassigned to a user
- Users without valid email address are now prompted on the main page to edit their profile
- Ability for administrators to disable users by editing a profile and setting status to Disabled Account.
- Force username to be unique when adding new users
- Do incident switchover when changing status via edit profie
- New report, average incident duration. Shows the time taken to close incidents over the months.
- When session expires and user logs in again the user is now redirected the the previously accessed page rather than the main page.
- Improved accuracy of SLA calculation
- Added ability to edit/delete software records
- When an inicdent is closed pending-reassignments are remove as necessary
- When an incident is closed any related incidents are notified of the closure.
- Added icons to priority selection dropdown for browsers that support it
- Improved sorting of some tables, you can now click again on the column header to sort in the opposite direction ascending/descending
- Holding queue locks now timeout after $CONFIG[record_lock_delay]
- Ability to delete multiple held emails in one go
- Ability to add resellers
- Escalation can now be configured via a database table, though there is no GUI for this yet
- External escalation partners can be configured via config file
- Edit incident now lets you select an escalation path (assuming paths are configured in the escalationpaths database table)
- Ability to add/edit/view tasks
- Ability to add notes to tasks
- Note owners can now delete their own notes
- Basic incoming email handler now included with SiT, as inboundemail.php
- New report incidents by software shows which software has the most incidents logged
- Tidied more HTML
- Fixed next action field, this is now stored and displayed again
- Interface to configure external escalation partners
- Made holiday booking easier
- Added ability to check which users have been granted each permission
<<lessSupport Incident Tracker project can manage contacts, sites, technical support contracts, and support incidents in one place. You can send and receive email directly from SiT!, attaching files and recording every communication in the incident log.
SiT! is aware of Service Level Agreements, and incidents are flagged if they stray outside of them.
Support Incident Tracker grew out of an application developed by Salford Software since 2000 called Webtrack and is used in-house by Support Engineers to easily track support incidents.
Enhancements:
- Fixed service levels for reopened incidents, service level target opened is now added making the next action initial response
- Fixed regression where mark for closure was ignored and the incident was closed immediately
- Lists number of incidents of each priority a user has on the user listings page.
- Show more accurately who last updated the call on list incidents pages
- Added multiple global signatures, one is choosen at random when email is sent.
- Fixed bug where disabled user accounts would still display as having relevant skills
- Fixed issue where URLs would not be shortened if they contained a % (percent) or $ (dollar) symbol
- Fixed issues with URLs that contain colons
- Incidents page informs you more accuratly who updated the call
- Specified MySQL Engine type to be MyISAM on all table creations
- Call opening notes are shown in tool tip after new incidents logged rather than reassign
- BB Code. Basic set of BB codes supported in incident updates
- Prevent summary and solution from being uncheck from close incident page since these are mandatory
- Fixed bug with not sending closing email
- send_template_email now store emails in the incident log
- Holiday calendar is now functional
- New holiday planner shows when all users are in/out
- Users can now be placed in groups, view users shows just your own group by default
- Users with edit user permission can set users holiday entitlement
- Able to change external escalation details on bulk
- View users now has links to Waiting queues and holiday calendars
- New interface for adding vendors
- Ability to request email notification when a call is reassigned to a user
- Users without valid email address are now prompted on the main page to edit their profile
- Ability for administrators to disable users by editing a profile and setting status to Disabled Account.
- Force username to be unique when adding new users
- Do incident switchover when changing status via edit profie
- New report, average incident duration. Shows the time taken to close incidents over the months.
- When session expires and user logs in again the user is now redirected the the previously accessed page rather than the main page.
- Improved accuracy of SLA calculation
- Added ability to edit/delete software records
- When an inicdent is closed pending-reassignments are remove as necessary
- When an incident is closed any related incidents are notified of the closure.
- Added icons to priority selection dropdown for browsers that support it
- Improved sorting of some tables, you can now click again on the column header to sort in the opposite direction ascending/descending
- Holding queue locks now timeout after $CONFIG[record_lock_delay]
- Ability to delete multiple held emails in one go
- Ability to add resellers
- Escalation can now be configured via a database table, though there is no GUI for this yet
- External escalation partners can be configured via config file
- Edit incident now lets you select an escalation path (assuming paths are configured in the escalationpaths database table)
- Ability to add/edit/view tasks
- Ability to add notes to tasks
- Note owners can now delete their own notes
- Basic incoming email handler now included with SiT, as inboundemail.php
- New report incidents by software shows which software has the most incidents logged
- Tidied more HTML
- Fixed next action field, this is now stored and displayed again
- Interface to configure external escalation partners
- Made holiday booking easier
- Added ability to check which users have been granted each permission
Download (1.2MB)
Added: 2006-11-06 License: GPL (GNU General Public License) Price:
1084 downloads
BrewNIX 1.0.2
BrewNIX is a brewing software project. more>>
BrewNIX is a brewing software project.
BrewNIX is beer brewing software that will primarily store recipes but also do some minor analysis of the recipes you enter.
It is currently a command line program, requiring curses. Future plans call for recipe compatibility with qbrew and a choice of GUI or CLI interface.
<<lessBrewNIX is beer brewing software that will primarily store recipes but also do some minor analysis of the recipes you enter.
It is currently a command line program, requiring curses. Future plans call for recipe compatibility with qbrew and a choice of GUI or CLI interface.
Download (0.12MB)
Added: 2006-11-14 License: GPL (GNU General Public License) Price:
1081 downloads
Grace Contribution Manager 0.2.2
Grace is a system of the Daniel Project that handles the tracking of contributions and donors for a non-profit. more>>
Grace project is a system of the Daniel Project that handles the tracking of contributions and donors for a non-profit. As contributions come in for particular funds, the contributions are recorded along with the donors information.
The system also handles the printing of receipts and reports, and facilitates common administrative operations like bank deposits and exporting of data to an accounting package.
Main features:
- Create a deposit and enter contributions into that deposit.
- Multiple line items (recipients) possible for each contribution.
- Streamlined data entry and finalizing of a deposit.
- Create multiple funds to receive contributions.
- Print receipts for donors.
- Print reports for fund owners (or output to PDF).
- Export to external accounting system.
- Notify fund owners by email of contributions.
- Multiple, concurrent users with extensive logging.
- Copy deposits for easy re-entry of repeated sets of contributions.
- Rapid, extensive search for deposits, contributions, and donors.
- GPL-licensed open source software for infinite flexibility to meet your needs.
Enhancements:
- Grace has been renamed to the Grace Contribution Manager (formerly Grace Receipting System).
- A splash screen is displayed on startup.
- New menu icons and a toolbar with shortcuts for frequently used operations.
- Two donors can now be merged into one using Other->Merge Donors...
- Two new reports: Major Donor Report and Donor Name Report.
- Receipts have been overhauled.
- This release runs on Windows.
<<lessThe system also handles the printing of receipts and reports, and facilitates common administrative operations like bank deposits and exporting of data to an accounting package.
Main features:
- Create a deposit and enter contributions into that deposit.
- Multiple line items (recipients) possible for each contribution.
- Streamlined data entry and finalizing of a deposit.
- Create multiple funds to receive contributions.
- Print receipts for donors.
- Print reports for fund owners (or output to PDF).
- Export to external accounting system.
- Notify fund owners by email of contributions.
- Multiple, concurrent users with extensive logging.
- Copy deposits for easy re-entry of repeated sets of contributions.
- Rapid, extensive search for deposits, contributions, and donors.
- GPL-licensed open source software for infinite flexibility to meet your needs.
Enhancements:
- Grace has been renamed to the Grace Contribution Manager (formerly Grace Receipting System).
- A splash screen is displayed on startup.
- New menu icons and a toolbar with shortcuts for frequently used operations.
- Two donors can now be merged into one using Other->Merge Donors...
- Two new reports: Major Donor Report and Donor Name Report.
- Receipts have been overhauled.
- This release runs on Windows.
Download (12.7MB)
Added: 2006-05-02 License: GPL (GNU General Public License) Price:
1275 downloads
File::Signature 1.009
File::Signature is a Perl module to detect changes to a files content or attributes. more>>
File::Signature is a Perl module to detect changes to a files content or attributes.
SYNOPSIS
use File::Signature;
my $sig = File::Signature->new(/some/file);
# If you have a stringified signature stored in $string
# you can create a File::Signature object from it.
my $sig = File::Signature->new_from_string($string);
if (my $err = $sig->error) {
warn $err, "n";
}
# You can use a signature object to re-check the same file.
if ( $sig->is_same() ) { print "Ok. The signature is the same.n" }
if ( $sig->changed() ) { print "Uh Oh! The signature has changed.n" }
my @digests = $sig->old_and_new(digest);
my @inodes = $sig->old_and_new(ino);
my @modes = $sig->old_and_new(mode);
my @uid = $sig->old_and_new(uid);
my @gid = $sig->old_and_new(gid);
my @mtime = $sig->old_and_new(mtime);
# A slightly more worthwhile use...
my @fields = $sig->changed();
for my $field (@fields) {
printf "$field was: %s but changed to %s.n",
$sig->old_and_new($field);
}
ABSTRACT
This perl library uses perl5 objects to assist in determining whether a files contents or attributes have changed. It maintains several pieces of information about the file: a digest (currently only MD5 is supported), its inode number, its mode, the uid of its owner, the gid of its group owner, and its last modification time. A File::Signature object is closely associated with a single pathname. It provides a way to compare the state of a file over different points in time; it isnt useful for comparing different files.
This module provides a way to monitor files for changes. It implements an object oriented interface to file "signatures." In the case of this module, a signature includes an MD5 digest (other digests may be added later), the files size, its inode number, its mode, its owners uid, its groups gid, and its mtime. This information is associated with a file by the files "pathname." The pathname is considered to be the files unique identifier. In reality, a file may have more than one pathname, but this module doesnt recognize that.
It will simply treat two differing pathnames as two different files, even if they refer to the same file. As this module checks whether a file changes over time, a minimal use of it would include the time when the signature was created and a different time when the signature is regenerated and compared with the previous one. The amount of time between these checks is arbitrary. This module makes it easy to save a signature object and then load it and check for consistency at a later time, whether seconds or years have passed.
<<lessSYNOPSIS
use File::Signature;
my $sig = File::Signature->new(/some/file);
# If you have a stringified signature stored in $string
# you can create a File::Signature object from it.
my $sig = File::Signature->new_from_string($string);
if (my $err = $sig->error) {
warn $err, "n";
}
# You can use a signature object to re-check the same file.
if ( $sig->is_same() ) { print "Ok. The signature is the same.n" }
if ( $sig->changed() ) { print "Uh Oh! The signature has changed.n" }
my @digests = $sig->old_and_new(digest);
my @inodes = $sig->old_and_new(ino);
my @modes = $sig->old_and_new(mode);
my @uid = $sig->old_and_new(uid);
my @gid = $sig->old_and_new(gid);
my @mtime = $sig->old_and_new(mtime);
# A slightly more worthwhile use...
my @fields = $sig->changed();
for my $field (@fields) {
printf "$field was: %s but changed to %s.n",
$sig->old_and_new($field);
}
ABSTRACT
This perl library uses perl5 objects to assist in determining whether a files contents or attributes have changed. It maintains several pieces of information about the file: a digest (currently only MD5 is supported), its inode number, its mode, the uid of its owner, the gid of its group owner, and its last modification time. A File::Signature object is closely associated with a single pathname. It provides a way to compare the state of a file over different points in time; it isnt useful for comparing different files.
This module provides a way to monitor files for changes. It implements an object oriented interface to file "signatures." In the case of this module, a signature includes an MD5 digest (other digests may be added later), the files size, its inode number, its mode, its owners uid, its groups gid, and its mtime. This information is associated with a file by the files "pathname." The pathname is considered to be the files unique identifier. In reality, a file may have more than one pathname, but this module doesnt recognize that.
It will simply treat two differing pathnames as two different files, even if they refer to the same file. As this module checks whether a file changes over time, a minimal use of it would include the time when the signature was created and a different time when the signature is regenerated and compared with the previous one. The amount of time between these checks is arbitrary. This module makes it easy to save a signature object and then load it and check for consistency at a later time, whether seconds or years have passed.
Download (0.008MB)
Added: 2007-04-30 License: Perl Artistic License Price:
909 downloads
PHP Active Code Library 0.10
PHP Active Code Library (ACL) is a PHP 5 class used to store and call PHP files that are stored in a database. more>>
PHP Active Code Library (ACL) is a PHP 5 class used to store and call PHP files that are stored in a database.
The files are stored in a plain text field and not a binary field. PHP ACL also takes care of include/require calls.
If a file includes another file stored in the database, PHP ACL takes care of getting, generating, and including that file.
<<lessThe files are stored in a plain text field and not a binary field. PHP ACL also takes care of include/require calls.
If a file includes another file stored in the database, PHP ACL takes care of getting, generating, and including that file.
Download (0.013MB)
Added: 2006-07-27 License: GPL (GNU General Public License) Price:
1191 downloads
SVNAccess 1.0.4
SVNAccess is a small Web application which lets one manage the access to SVN repositories through a simple interface. more>>
SVNAccess is a small Web application which lets one manage the access to SVN repositories through a simple interface.
SVNAccess uses existing Apache password files/users and stores information in a MySQL database in order to generate an AuthzSVNAccessFile formatted access file.
One can also delegate admin rights to a group and repository access to users so that repository owners can manage their own access.
<<lessSVNAccess uses existing Apache password files/users and stores information in a MySQL database in order to generate an AuthzSVNAccessFile formatted access file.
One can also delegate admin rights to a group and repository access to users so that repository owners can manage their own access.
Download (0.010MB)
Added: 2007-06-19 License: GPL (GNU General Public License) Price:
857 downloads
online-bookmarks 0.6.9
online-bookmarks is a bookmarks management system to store bookmarks, favorites, and links on the WWW. more>>
online-bookmarks is a bookmarks management system to store bookmarks, favorites, and links on the WWW where they actually belong.
online-bookmarks projects is meant for people who work often with different computers and browsers. It supports multiple users, multiple languages, and has a folder structure of arbitrary depth.
Importing and exporting bookmarks from and to Opera, Netscape, Mozilla, and Internet Explorer are possible.
<<lessonline-bookmarks projects is meant for people who work often with different computers and browsers. It supports multiple users, multiple languages, and has a folder structure of arbitrary depth.
Importing and exporting bookmarks from and to Opera, Netscape, Mozilla, and Internet Explorer are possible.
Download (0.047MB)
Added: 2006-07-13 License: GPL (GNU General Public License) Price:
1200 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above store owners search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
