names and addresses
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 4934
My Address Book 1.2
My Address Book is a Web-based contact list program. more>>
My Address Book is a Web-based contact list program. It stores information like addresses, phone numbers, email addresses, and Web sites, and has a notes section for custom information.
Add, delete, and edit functions can be password protected using htaccess. Complete style control using CSS.
Main features:
- Add an unlimited number of contacts.
- Easy to use and read.
- Specify your own colors.
- Use your own template.
<<lessAdd, delete, and edit functions can be password protected using htaccess. Complete style control using CSS.
Main features:
- Add an unlimited number of contacts.
- Easy to use and read.
- Specify your own colors.
- Use your own template.
Download (0.016MB)
Added: 2005-10-19 License: GPL (GNU General Public License) Price:
1473 downloads
DNS name parser 1.2.1
DNS name parser is a Java utility library for parsing dns names, ip and hw addresses. more>>
DNS name parser is a Java utility library for parsing dns names, ip and hw addresses.
Synopsis
import su.netdb.parser.*;
Parser parser = new Parser();
Hashtable result = parser.parse(str);
System.out.println("string: "+result.get("string"));
System.out.println("hw: "+result.get("hw"));
System.out.println("name: "+result.get("name"));
System.out.println("domain: "+result.get("domain"));
System.out.println("ip_low: "+result.get("ip_low"));
System.out.println("ip_high: "+result.get("ip_high"));
"DNS name parser" is an utility library created to be used in a search application. Given a single input field its function is to differentiate between several types of possible input strings. Namely if it a dns name, IP address (exact, ip range or ip with wildcards) or hardware address. The result of the parsing is a Hashtable with possible keys "string", "hw", "name", "domain", "ip_low" and "ip_high".
<<lessSynopsis
import su.netdb.parser.*;
Parser parser = new Parser();
Hashtable result = parser.parse(str);
System.out.println("string: "+result.get("string"));
System.out.println("hw: "+result.get("hw"));
System.out.println("name: "+result.get("name"));
System.out.println("domain: "+result.get("domain"));
System.out.println("ip_low: "+result.get("ip_low"));
System.out.println("ip_high: "+result.get("ip_high"));
"DNS name parser" is an utility library created to be used in a search application. Given a single input field its function is to differentiate between several types of possible input strings. Namely if it a dns name, IP address (exact, ip range or ip with wildcards) or hardware address. The result of the parsing is a Hashtable with possible keys "string", "hw", "name", "domain", "ip_low" and "ip_high".
Download (0.008MB)
Added: 2007-07-20 License: GPL (GNU General Public License) Price:
835 downloads
Geo::StreetAddress::US 0.99
Geo::StreetAddress::US is a Perl extension for parsing US street addresses. more>>
Geo::StreetAddress::US is a Perl extension for parsing US street addresses.
SYNOPSIS
use Geo::StreetAddress::US;
my $hashref = Geo::StreetAddress::US->parse_location(
"1005 Gravenstein Hwy N, Sebastopol CA 95472" );
my $hashref = Geo::StreetAddress::US->parse_location(
"Hollywood & Vine, Los Angeles, CA" );
my $hashref = Geo::StreetAddress::US->parse_address(
"1600 Pennsylvania Ave, Washington, DC" );
my $hashref = Geo::StreetAddress::US->parse_intersection(
"Mission Street at Valencia Street, San Francisco, CA" );
my $normal = Geo::StreetAddress::US->normalize_address( %spec );
# the parse_* methods call this automatically...
Geo::StreetAddress::US is a regex-based street address and street intersection parser for the United States. Its basic goal is to be as forgiving as possible when parsing user-provided address strings.
Geo::StreetAddress::US knows about directional prefixes and suffixes, fractional building numbers, building units, grid-based addresses (such as those used in parts of Utah), 5 and 9 digit ZIP codes, and all of the official USPS abbreviations for street types and state names.
<<lessSYNOPSIS
use Geo::StreetAddress::US;
my $hashref = Geo::StreetAddress::US->parse_location(
"1005 Gravenstein Hwy N, Sebastopol CA 95472" );
my $hashref = Geo::StreetAddress::US->parse_location(
"Hollywood & Vine, Los Angeles, CA" );
my $hashref = Geo::StreetAddress::US->parse_address(
"1600 Pennsylvania Ave, Washington, DC" );
my $hashref = Geo::StreetAddress::US->parse_intersection(
"Mission Street at Valencia Street, San Francisco, CA" );
my $normal = Geo::StreetAddress::US->normalize_address( %spec );
# the parse_* methods call this automatically...
Geo::StreetAddress::US is a regex-based street address and street intersection parser for the United States. Its basic goal is to be as forgiving as possible when parsing user-provided address strings.
Geo::StreetAddress::US knows about directional prefixes and suffixes, fractional building numbers, building units, grid-based addresses (such as those used in parts of Utah), 5 and 9 digit ZIP codes, and all of the official USPS abbreviations for street types and state names.
Download (0.010MB)
Added: 2006-09-25 License: Perl Artistic License Price:
1124 downloads
Mail::RFC822::Address 0.3
Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822. more>>
Mail::RFC822::Address is a Perl extension for validating email addresses according to RFC822.
SYNOPSIS
use Mail::RFC822::Address qw(valid validlist);
if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}
if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}
Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.
This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.
valid ( address )
Returns true or false to indicate if address is an RFC822 valid address.
validlist ( addresslist )
In scalar context, returns true if the parameter is an RFC822 valid list of addresses.
In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list
<<lessSYNOPSIS
use Mail::RFC822::Address qw(valid validlist);
if (valid("pdw@ex-parrot.com")) {
print "Thats a valid addressn";
}
if (validlist("pdw@ex-parrot.com, other@elsewhere.com")) {
print "Thats a valid list of addressesn";
}
Mail::RFC822::Address validates email addresses against the grammar described in RFC 822 using regular expressions. How to validate a user supplied email address is a FAQ (see perlfaq9): the only sure way to see if a supplied email address is genuine is to send an email to it and see if the user recieves it. The one useful check that can be performed on an address is to check that the email address is syntactically valid. That is what this module does.
This module is functionally equivalent to RFC::RFC822::Address, but uses regular expressions rather than the Parse::RecDescent parser. This means that startup time is greatly reduced making it suitable for use in transient scripts such as CGI scripts.
valid ( address )
Returns true or false to indicate if address is an RFC822 valid address.
validlist ( addresslist )
In scalar context, returns true if the parameter is an RFC822 valid list of addresses.
In list context, returns an empty list on failure (an invalid address was found); otherwise a list whose first element is the number of addresses found and whose remaining elements are the addresses. This is needed to disambiguate failure (invalid) from success with no addresses found, because an empty string is a valid list
Download (0.005MB)
Added: 2007-02-14 License: Perl Artistic License Price:
985 downloads
Google::Adwords::Address 0.6.0
Google::Adwords::Address is a Google Adwords Address object. more>>
Google::Adwords::Address is a Google Adwords Address object.
SYNOPSIS
use Google::Adwords::Address;
my $address = Google::Adwords::Address->new
->addressLine1(first street)
->city(Paris)
->companyName(My company)
->countryCode(FR)
->emailAddress(my@example.com);
This object should be used with the AccountService API calls
METHODS
Mutators (read/write)
- addressLine1
- addressLine2
- city
- companyName
- countryCode
- emailAddress
- faxNumber
- name
- phoneNumber
- postalCode
- state
<<lessSYNOPSIS
use Google::Adwords::Address;
my $address = Google::Adwords::Address->new
->addressLine1(first street)
->city(Paris)
->companyName(My company)
->countryCode(FR)
->emailAddress(my@example.com);
This object should be used with the AccountService API calls
METHODS
Mutators (read/write)
- addressLine1
- addressLine2
- city
- companyName
- countryCode
- emailAddress
- faxNumber
- name
- phoneNumber
- postalCode
- state
Download (0.041MB)
Added: 2006-11-23 License: Perl Artistic License Price:
1067 downloads
Autocomplete Manager 1.6
Autocomplete Manager is an extension which provides advanced features for the address Autocomplete component in Firefox. more>>
Autocomplete Manager is an extension which provides advanced features for the address Autocomplete component in Firefox.
This extension provides advanced features for the address Autocomplete component in Firefox. It has been tested on Windows XP and Vista, Linux (Fedora Core 4), and Mac OS X.
Main features:
- searching bookmark addresses
- matching against page titles and bookmark names
- changing the sorting criterion to alphabetical, most-often-visited, most-recently-visited, or top-level pages first
- opening a suggestion from the popup in a new tab
- excluding local pages and pages containing search results
- matching any part of the domain
- popup appearance fine-tuning, including hiding page titles, changing the number of visible entries, and setting the truncation method for long addresses and page titles
In addition, one can switch between the default and the enhanced Autocomplete component, or turn it off altogether. The extension includes numerous fixes for Autocomplete-related bugs, as well as a rudimentary history manager, which can be used to view, add, and delete history entries.
<<lessThis extension provides advanced features for the address Autocomplete component in Firefox. It has been tested on Windows XP and Vista, Linux (Fedora Core 4), and Mac OS X.
Main features:
- searching bookmark addresses
- matching against page titles and bookmark names
- changing the sorting criterion to alphabetical, most-often-visited, most-recently-visited, or top-level pages first
- opening a suggestion from the popup in a new tab
- excluding local pages and pages containing search results
- matching any part of the domain
- popup appearance fine-tuning, including hiding page titles, changing the number of visible entries, and setting the truncation method for long addresses and page titles
In addition, one can switch between the default and the enhanced Autocomplete component, or turn it off altogether. The extension includes numerous fixes for Autocomplete-related bugs, as well as a rudimentary history manager, which can be used to view, add, and delete history entries.
Download (0.069MB)
Added: 2007-05-21 License: MPL (Mozilla Public License) Price:
909 downloads
My Address Book contacts manager 0.9.5
My Address Book is a web-based address book designed to help you keep a record of your friends addresses. more>>
My Address Book is a web-based address book designed to help you keep a record of your friends addresses, providing a list of your contacts (which may be filtered), categories, details of a particular contact, export and import of data (e.g. from spreadsheets), and a Christmas card list.
To use My Address Book you need to have access to some web space that allows you to use PHP and MySQL. If you want your address book to be private (which is highly recommended!) you will need to set it up inside a password-protected directory in your web space.
Installation:
If you want to use My Address Book over the Internet so you can access your addresses wherever you are, you will need some web space which allows you to use PHP and MySQL. If you only want to use My Address Book on a single computer, you will need a web server (e.g. Apache) which supports PHP and you will need MySQL.
Enhancements:
- The dates of birth of contacts may now be stored.
<<lessTo use My Address Book you need to have access to some web space that allows you to use PHP and MySQL. If you want your address book to be private (which is highly recommended!) you will need to set it up inside a password-protected directory in your web space.
Installation:
If you want to use My Address Book over the Internet so you can access your addresses wherever you are, you will need some web space which allows you to use PHP and MySQL. If you only want to use My Address Book on a single computer, you will need a web server (e.g. Apache) which supports PHP and you will need MySQL.
Enhancements:
- The dates of birth of contacts may now be stored.
Download (0.093MB)
Added: 2006-02-21 License: GPL (GNU General Public License) Price:
1340 downloads
RFC822 Address Parser Library 1.2
RFC822 Address Parser Library provides application developers with a complete parser for RFC822 addresses. more>>
RFC822 Address Parser Library provides application developers with a complete parser for RFC822 addresses. Not only can you use the library to verify that RFC822 addresses are syntactically correct, you can also have an address split up into its semantic parts, what is needed when deciding where to route an address to, etc.
What is quite unique is that librfc822 does indeed parse all address types allowed by the standard. That includes such weird things as "address groups" or addresses with whitespace and comments throw in. Take a look at this beast to get an idea:
testing my parser : peter.simons@gmd.de,
(peter.)simons@rhein.de ,,,,,
testing my parser ,
it rules < @peti.gmd.de,@listserv.gmd.de:simons @ cys .de >
;
,
peter.simons@acm.org
That is indeed a legal e-mail address in RFC822 messages. It contains five separate addresses, which are grouped together. Heres the parsed result:
peter.simons@gmd.de
simons@rhein.de
simons@ieee.org
< @peti.gmd.de,@listserv.gmd.de:simons@cys.de >
peter.simons@acm.org
simons@rhein.de
simons@rhein.de
simons@rhein.de
In case you wonder: The strange looking address thats listed fourth is a so called "routing address" -- and yes, thats a legal e-mail address, too. These were popular in the early days of the Internet. Back then, every mail server that relayed an e-mail put its own address into this construct so that bounces could be routed the same way back that they originally went.
The address says that the mail should be send to the host peti.gmd.de, then to listserv.gmd.de, and from there it should be delivered (using any route) to the address simons@cys.de. These days, such addresses can hardly be used, because nobody relays for other recipients anymore. Still, these are legal.
librfc822 provides you with several routines that parse the different flavours of e-mail addresses as defined in the standard. The results will be placed in a rfc822address structure and returned. If constructs are parsed that may contain multiple addresses, you can pass a "committer" class to the function, which is called every time a correct address is found and may append it to a container of your choice.
Enhancements:
- The library has been re-released under an all-permissive license.
<<lessWhat is quite unique is that librfc822 does indeed parse all address types allowed by the standard. That includes such weird things as "address groups" or addresses with whitespace and comments throw in. Take a look at this beast to get an idea:
testing my parser : peter.simons@gmd.de,
(peter.)simons@rhein.de ,,,,,
testing my parser ,
it rules < @peti.gmd.de,@listserv.gmd.de:simons @ cys .de >
;
,
peter.simons@acm.org
That is indeed a legal e-mail address in RFC822 messages. It contains five separate addresses, which are grouped together. Heres the parsed result:
peter.simons@gmd.de
simons@rhein.de
simons@ieee.org
< @peti.gmd.de,@listserv.gmd.de:simons@cys.de >
peter.simons@acm.org
simons@rhein.de
simons@rhein.de
simons@rhein.de
In case you wonder: The strange looking address thats listed fourth is a so called "routing address" -- and yes, thats a legal e-mail address, too. These were popular in the early days of the Internet. Back then, every mail server that relayed an e-mail put its own address into this construct so that bounces could be routed the same way back that they originally went.
The address says that the mail should be send to the host peti.gmd.de, then to listserv.gmd.de, and from there it should be delivered (using any route) to the address simons@cys.de. These days, such addresses can hardly be used, because nobody relays for other recipients anymore. Still, these are legal.
librfc822 provides you with several routines that parse the different flavours of e-mail addresses as defined in the standard. The results will be placed in a rfc822address structure and returned. If constructs are parsed that may contain multiple addresses, you can pass a "committer" class to the function, which is called every time a correct address is found and may append it to a container of your choice.
Enhancements:
- The library has been re-released under an all-permissive license.
Download (0.094MB)
Added: 2007-05-13 License: Freeware Price:
895 downloads
Yukatan data model 1.0
Yukatan data model project is the schema definition of the Yukatan webmail database. more>>
Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented
<<lessThe PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented
Download (0.035MB)
Added: 2007-02-19 License: GPL (GNU General Public License) Price:
983 downloads
The Worlds Best Band Name Generator 1.03
The Worlds Best Band Name Generator produces randomly generated band names. more>>
The Worlds Best Band Name Generator produces randomly generated band names.
The Worlds Best Band Name Generator can generate band names like "Ungratefully Swallowed" and "The Bridgeheads" and "Throwaway Deceptiveness".
The visitor can refresh the names dynamically without refreshing the page by using a small AJAX script.
The generator uses combinations of nouns, adjectives, and adverbs that lend themselves well to band name creation, so most of the names actually sound realistic.
The script is easy to install and modify.
You can download the Worlds Best Band Name Generator for FREE to add to your own web site.
If you really like the Words Best Band Name Generator, please link to this page so other people can find it.
<<lessThe Worlds Best Band Name Generator can generate band names like "Ungratefully Swallowed" and "The Bridgeheads" and "Throwaway Deceptiveness".
The visitor can refresh the names dynamically without refreshing the page by using a small AJAX script.
The generator uses combinations of nouns, adjectives, and adverbs that lend themselves well to band name creation, so most of the names actually sound realistic.
The script is easy to install and modify.
You can download the Worlds Best Band Name Generator for FREE to add to your own web site.
If you really like the Words Best Band Name Generator, please link to this page so other people can find it.
Download (0.45MB)
Added: 2005-12-02 License: Freeware Price:
1425 downloads
Nmap::Scanner 0.9
Nmap::Scanner is a Perl module to perform and manipulate nmap scans using perl. more>>
Nmap::Scanner is a Perl module to perform and manipulate nmap scans using perl.
SYNOPSIS
Perl extension for performing nmap (www.insecure.org/nmap) scans.
use Nmap::Scanner;
# Batch scan method
my $scanner = new Nmap::Scanner;
$scanner->tcp_syn_scan();
$scanner->add_scan_port(1-1024);
$scanner->add_scan_port(8080);
$scanner->guess_os();
$scanner->max_rtt_timeout(200);
$scanner->add_target(some.host.out.there.com.org);
# $results is an instance of Nmap::Scanner::Backend::Results
my $results = $scanner->scan();
# Print the results out as an well-formatted XML document
print $results->as_xml();
# Event scan method using *new* easier way to set scan options.
my $scanner = new Nmap::Scanner;
$scanner->register_scan_started_event(&scan_started);
$scanner->register_port_found_event(&port_found);
$scanner->scan(-sS -p 1-1024 -O --max-rtt-timeout 200 somehost.org.net.it);
sub scan_started {
my $self = shift;
my $host = shift;
my $hostname = $host->name();
my $addresses = join(,, map {$_->address()} $host->addresses());
my $status = $host->status();
print "$hostname ($addresses) is $statusn";
}
sub port_found {
my $self = shift;
my $host = shift;
my $port = shift;
my $name = $host->name();
my $addresses = join(,, map {$_->addr()} $host->addresses());
print "On host $name ($addresses), found ",
$port->state()," port ",
join(/,$port->protocol(),$port->portid()),"n";
}
This set of modules provides perl class wrappers for the network mapper (nmap) scanning tool (see http://www.insecure.org/nmap/). Using these modules, a developer, network administrator, or other techie can create perl routines or classes which can be used to automate and integrate nmap scans elegantly into new and existing perl scripts.
If you dont have nmap installed, you will need to download it BEFORE you can use these modules. Get it from http://www.insecure.org/nmap/. You will need nmap 3.10+ installed to use all the features of this module.
<<lessSYNOPSIS
Perl extension for performing nmap (www.insecure.org/nmap) scans.
use Nmap::Scanner;
# Batch scan method
my $scanner = new Nmap::Scanner;
$scanner->tcp_syn_scan();
$scanner->add_scan_port(1-1024);
$scanner->add_scan_port(8080);
$scanner->guess_os();
$scanner->max_rtt_timeout(200);
$scanner->add_target(some.host.out.there.com.org);
# $results is an instance of Nmap::Scanner::Backend::Results
my $results = $scanner->scan();
# Print the results out as an well-formatted XML document
print $results->as_xml();
# Event scan method using *new* easier way to set scan options.
my $scanner = new Nmap::Scanner;
$scanner->register_scan_started_event(&scan_started);
$scanner->register_port_found_event(&port_found);
$scanner->scan(-sS -p 1-1024 -O --max-rtt-timeout 200 somehost.org.net.it);
sub scan_started {
my $self = shift;
my $host = shift;
my $hostname = $host->name();
my $addresses = join(,, map {$_->address()} $host->addresses());
my $status = $host->status();
print "$hostname ($addresses) is $statusn";
}
sub port_found {
my $self = shift;
my $host = shift;
my $port = shift;
my $name = $host->name();
my $addresses = join(,, map {$_->addr()} $host->addresses());
print "On host $name ($addresses), found ",
$port->state()," port ",
join(/,$port->protocol(),$port->portid()),"n";
}
This set of modules provides perl class wrappers for the network mapper (nmap) scanning tool (see http://www.insecure.org/nmap/). Using these modules, a developer, network administrator, or other techie can create perl routines or classes which can be used to automate and integrate nmap scans elegantly into new and existing perl scripts.
If you dont have nmap installed, you will need to download it BEFORE you can use these modules. Get it from http://www.insecure.org/nmap/. You will need nmap 3.10+ installed to use all the features of this module.
Download (0.066MB)
Added: 2007-04-11 License: Perl Artistic License Price:
943 downloads
RFC::RFC822::Address 1.5
RFC::RFC822::Address is a Perl module for RFC 822 style address validation. more>>
RFC::RFC822::Address is a Perl module for RFC 822 style address validation.
SYNOPSIS
use RFC::RFC822::Address qw /valid/;
print "Validn" if valid abigail@example.com;
This module checks strings to see whether they are have the valid syntax, as defined in RFC 822 [1]. One subroutine, valid, can be imported, which takes a single string as argument. If the string is valid according to RFC 822, a true value is returned, else a false value is returned.
CAVEATS and BUGS
This module sets the variable $Parse::RecDescent::skip. This will influence all other Parse::RecDescent parsers. And this parser will break if you set $Parse::RecDescent::skip to another value. It doesnt look that it is possible to set an alternative skip value for each parser, other than setting the skip value on each production.
Example A.1.5 in RFC 822 is wrong. It should use "Galloping Gourmet"@ANT.Down-Under.
This module should have been named RFC::822::Address. However, perl 5.004 doesnt like the 822 part, and at the time of this writing MacPerl is still at 5.004.
This module is slow.
<<lessSYNOPSIS
use RFC::RFC822::Address qw /valid/;
print "Validn" if valid abigail@example.com;
This module checks strings to see whether they are have the valid syntax, as defined in RFC 822 [1]. One subroutine, valid, can be imported, which takes a single string as argument. If the string is valid according to RFC 822, a true value is returned, else a false value is returned.
CAVEATS and BUGS
This module sets the variable $Parse::RecDescent::skip. This will influence all other Parse::RecDescent parsers. And this parser will break if you set $Parse::RecDescent::skip to another value. It doesnt look that it is possible to set an alternative skip value for each parser, other than setting the skip value on each production.
Example A.1.5 in RFC 822 is wrong. It should use "Galloping Gourmet"@ANT.Down-Under.
This module should have been named RFC::822::Address. However, perl 5.004 doesnt like the 822 part, and at the time of this writing MacPerl is still at 5.004.
This module is slow.
Download (1.5MB)
Added: 2007-02-15 License: Perl Artistic License Price:
987 downloads
Bulletin Board News Server .11
Bulletin Board News Server provides a (v)Bulletin Board NNTP interface. more>>
Bulletin Board News Server provides a (v)Bulletin Board NNTP interface.
Bulletin Board News Server is a (relatively) quick NNTP interface for vBulletin. It reads directly from the MySQL DB and is therefore independent of the Web frontend.
It doesnt alter read counters, but "forbidden names", name size limitations, user authentication, and anonymous posting (through a "usenet" user) are implemented.
Registered users (either in the vboard or through a proprietary pw hash in the config file) can see the email addresses of others, as far as the owners permit it.
<<lessBulletin Board News Server is a (relatively) quick NNTP interface for vBulletin. It reads directly from the MySQL DB and is therefore independent of the Web frontend.
It doesnt alter read counters, but "forbidden names", name size limitations, user authentication, and anonymous posting (through a "usenet" user) are implemented.
Registered users (either in the vboard or through a proprietary pw hash in the config file) can see the email addresses of others, as far as the owners permit it.
Download (0.026MB)
Added: 2007-03-29 License: GPL (GNU General Public License) Price:
951 downloads
GNU adns 1.0
GNU adns is a resolver library for C and C++ programs. more>>
GNU adns is a resolver library for C and C++ programs.
Includes automatic sanity checking and responses that are automatically decoded into a natural C representation. Very easy to use for simple programs that just want to look up MX records or translate names to addresses.
Time-to-live, CNAME, and similar information are returned in an easy to use manner, and you can launch many queries at once and deal with the replies asynchronously. The program reports errors in a way that distinguishes the cause of failure.
Main features:
- It is reasonably easy to use for simple programs which just want to translate names to addresses, look up MX records, etc.
- It can be used in an asynchronous, non-blocking, manner. Many queries can be handled simultaneously.
- Responses are decoded automatically into a natural representation for a C program - there is no need to deal with DNS packet formats.
- Sanity checking (eg, name syntax checking, reverse/forward correspondence, CNAME pointing to CNAME) is performed automatically.
- Time-to-live, CNAME and other similar information is returned in an easy-to-use form, without getting in the way.
- There is no global state in the library; resolver state is an opaque data structure which the client creates explicitly. A program can have several instances of the resolver.
- Errors are reported to the application in a way that distinguishes the various causes of failure properly.
- Understands conventional resolv.conf, but this can overridden by environment variables.
- Flexibility. For example, the application can tell adns to: ignore environment variables (for setuid programs), disable hostname syntax sanity checks to return arbitrary data, override or ignore resolv.conf in favour of supplied configuration, etc.
- Believed to be correct ! For example, will correctly back off to TCP in case of long replies or queries, or to other nameservers if several are available. It has sensible handling of bad responses etc.
<<lessIncludes automatic sanity checking and responses that are automatically decoded into a natural C representation. Very easy to use for simple programs that just want to look up MX records or translate names to addresses.
Time-to-live, CNAME, and similar information are returned in an easy to use manner, and you can launch many queries at once and deal with the replies asynchronously. The program reports errors in a way that distinguishes the cause of failure.
Main features:
- It is reasonably easy to use for simple programs which just want to translate names to addresses, look up MX records, etc.
- It can be used in an asynchronous, non-blocking, manner. Many queries can be handled simultaneously.
- Responses are decoded automatically into a natural representation for a C program - there is no need to deal with DNS packet formats.
- Sanity checking (eg, name syntax checking, reverse/forward correspondence, CNAME pointing to CNAME) is performed automatically.
- Time-to-live, CNAME and other similar information is returned in an easy-to-use form, without getting in the way.
- There is no global state in the library; resolver state is an opaque data structure which the client creates explicitly. A program can have several instances of the resolver.
- Errors are reported to the application in a way that distinguishes the various causes of failure properly.
- Understands conventional resolv.conf, but this can overridden by environment variables.
- Flexibility. For example, the application can tell adns to: ignore environment variables (for setuid programs), disable hostname syntax sanity checks to return arbitrary data, override or ignore resolv.conf in favour of supplied configuration, etc.
- Believed to be correct ! For example, will correctly back off to TCP in case of long replies or queries, or to other nameservers if several are available. It has sensible handling of bad responses etc.
Download (0.24MB)
Added: 2006-06-07 License: GPL (GNU General Public License) Price:
1236 downloads
Twisted Names 0.3.0
Twisted Names is both a domain name server as well as a client resolver library. more>>
Twisted Names project is both a domain name server as well as a client resolver library.
Twisted Names comes with an "out of the box" nameserver which can read most BIND-syntax zone files as well as a simple Python-based configuration format.
Twisted Names can act as an authoritative server, perform zone transfers from a master to act as a secondary, act as a caching nameserver, or any combination of these.
Twisted Names client resolver library provides functions to query for all commonly used record types as well as a replacement for the blocking gethostbyname() function provided by the Python stdlib socket module.
Twisted Names is available under the MIT Free Software licence.
Enhancements:
- Errors in the markup used in API documentation have been fixed.
- A bug where the DNS client would sometimes drop a response has been fixed.
- A bug which prevented non-IN lookups from generating malformed queries has been fixed.
<<lessTwisted Names comes with an "out of the box" nameserver which can read most BIND-syntax zone files as well as a simple Python-based configuration format.
Twisted Names can act as an authoritative server, perform zone transfers from a master to act as a secondary, act as a caching nameserver, or any combination of these.
Twisted Names client resolver library provides functions to query for all commonly used record types as well as a replacement for the blocking gethostbyname() function provided by the Python stdlib socket module.
Twisted Names is available under the MIT Free Software licence.
Enhancements:
- Errors in the markup used in API documentation have been fixed.
- A bug where the DNS client would sometimes drop a response has been fixed.
- A bug which prevented non-IN lookups from generating malformed queries has been fixed.
Download (0.028MB)
Added: 2006-05-28 License: MIT/X Consortium License Price:
1246 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 names and addresses 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