messages
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2350
Locale::Messages 1.16
Locale::Messages is a Perl module with Gettext Like Message Retrieval. more>>
Locale::Messages is a Perl module with Gettext Like Message Retrieval.
SYNOPSIS
use Locale::Messages (:locale_h :libintl_h);
gettext $msgid;
dgettext $textdomain, $msgid;
dcgettext $textdomain, $msgid, LC_MESSAGES;
ngettext $msgid, $msgid_plural, $count;
dngettext $textdomain, $msgid, $msgid_plural, $count;
dcngettext $textdomain, $msgid, $msgid_plural, $count, LC_MESSAGES;
textdomain $textdomain;
bindtextdomain $textdomain, $directory;
bind_textdomain_codeset $textdomain, $encoding;
bind_textdomain_filter $textdomain, &filter, $data;
turn_utf_8_on ($variable);
turn_utf_8_off ($variable);
nl_putenv (OUTPUT_CHARSET=koi8-r);
my $category = LC_CTYPE;
my $category = LC_NUMERIC;
my $category = LC_TIME;
my $category = LC_COLLATE;
my $category = LC_MONETARY;
my $category = LC_MESSAGES;
my $category = LC_ALL;
The module Locale::Messages is a wrapper around the interface to message translation according to the Uniforum approach that is for example used in GNU gettext and Suns Solaris. It is intended to allow Locale::Messages(3) to switch between different implementations of the lower level libraries but this is not yet implemented.
Normally you should not use this module directly, but the high level interface Locale::TextDomain(3) that provides a much simpler interface. This description is therefore deliberately kept brief. Please refer to the GNU gettext documentation available at http://www.gnu.org/manual/gettext/ for in-depth and background information on the topic.
The lower level module Locale::gettext_pp(3) provides the Perl implementation of gettext() and related functions.
<<lessSYNOPSIS
use Locale::Messages (:locale_h :libintl_h);
gettext $msgid;
dgettext $textdomain, $msgid;
dcgettext $textdomain, $msgid, LC_MESSAGES;
ngettext $msgid, $msgid_plural, $count;
dngettext $textdomain, $msgid, $msgid_plural, $count;
dcngettext $textdomain, $msgid, $msgid_plural, $count, LC_MESSAGES;
textdomain $textdomain;
bindtextdomain $textdomain, $directory;
bind_textdomain_codeset $textdomain, $encoding;
bind_textdomain_filter $textdomain, &filter, $data;
turn_utf_8_on ($variable);
turn_utf_8_off ($variable);
nl_putenv (OUTPUT_CHARSET=koi8-r);
my $category = LC_CTYPE;
my $category = LC_NUMERIC;
my $category = LC_TIME;
my $category = LC_COLLATE;
my $category = LC_MONETARY;
my $category = LC_MESSAGES;
my $category = LC_ALL;
The module Locale::Messages is a wrapper around the interface to message translation according to the Uniforum approach that is for example used in GNU gettext and Suns Solaris. It is intended to allow Locale::Messages(3) to switch between different implementations of the lower level libraries but this is not yet implemented.
Normally you should not use this module directly, but the high level interface Locale::TextDomain(3) that provides a much simpler interface. This description is therefore deliberately kept brief. Please refer to the GNU gettext documentation available at http://www.gnu.org/manual/gettext/ for in-depth and background information on the topic.
The lower level module Locale::gettext_pp(3) provides the Perl implementation of gettext() and related functions.
Download (0.45MB)
Added: 2007-03-06 License: Perl Artistic License Price:
962 downloads
cintoo Messages 1.0 Alpha1
cintoo Messages is a framework to make internationalization easier for Java applications. more>>
cintoo Messages is a framework to make internationalization easier for Java applications. cintoo Messages framework supports locales for threads, and bundles can be associated with different packages.
This allows the usage of different bundles for different parts of the application, such as plugins, an installer, or a logging system. Bundles can be managed and associated with packages without any changes in the code.
This makes bundle management and refactoring much easier than with other solutions. cintoo Messages supports global locales for client applications written in Swing or SWT and thread-local ones for serverside Web applications.
Example:
Messages.setBundle("myBundle", "only.for.this.package");
...
Messages.setThreadLocale(new Locale("en", ""));
...
Messages.format(this, "myKey");
<<lessThis allows the usage of different bundles for different parts of the application, such as plugins, an installer, or a logging system. Bundles can be managed and associated with packages without any changes in the code.
This makes bundle management and refactoring much easier than with other solutions. cintoo Messages supports global locales for client applications written in Swing or SWT and thread-local ones for serverside Web applications.
Example:
Messages.setBundle("myBundle", "only.for.this.package");
...
Messages.setThreadLocale(new Locale("en", ""));
...
Messages.format(this, "myKey");
Download (0.030MB)
Added: 2006-05-08 License: The Apache License 2.0 Price:
1269 downloads
Message::Style 0.002
Message::Style is a Perl module to perform stylistic analysis of messages. more>>
Message::Style is a Perl module to perform stylistic analysis of messages.
SYNOPSIS
use Message::Style;
my $score=Message::Style::score(@article);
# or
my $score=Message::Style::score(@article);
This Perl library does an analysis of a RFC2822 format message (typically email messages or Usenet posts) and produces a score that, in the authors opinion, gives a good indication as to whether the poster is a fsckwit, and therefore whether their message should be ignored.
<<lessSYNOPSIS
use Message::Style;
my $score=Message::Style::score(@article);
# or
my $score=Message::Style::score(@article);
This Perl library does an analysis of a RFC2822 format message (typically email messages or Usenet posts) and produces a score that, in the authors opinion, gives a good indication as to whether the poster is a fsckwit, and therefore whether their message should be ignored.
Download (0.005MB)
Added: 2006-08-29 License: Perl Artistic License Price:
1153 downloads
Wily::Message 0.02
Wily::Message is a Perl extension to handle Wily Messages. more>>
Wily::Message is a Perl extension to handle Wily Messages.
SYNOPSIS
use Wily::Message;
use Wily::Connect;
# opens a file in wily and exits when the window is destroyed
my $win_id;
my $ws = Wily::Connect::connect();
my $wm = Wily::Message->new(Wily::Message::WMnew, 0, 0, 0, 1,
/tmp/file_to_edit);
$ws->syswrite($wm->flatten());
my $buffer = ;
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMnew: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRnew) {
$win_id = $wm->{window_id};
$wm = Wily::Message->new(Wily::Message::WMattach, $win_id, 0, 0,
Wily::Message::WEdestroy);
$ws->syswrite($wm->flatten());
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMattach: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRattach) {
} else {
die "Expected a WRattach, but didnt get one";
}
} else {
die "Expected a WRnew, but didnt get one";
}
while (1) {
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WEdestroy and $wm->{window_id} == $win_id) {
last;
}
}
A simple object wrapper around Wily messages with a helper function to assist in extracting messages from the wily connection.
<<lessSYNOPSIS
use Wily::Message;
use Wily::Connect;
# opens a file in wily and exits when the window is destroyed
my $win_id;
my $ws = Wily::Connect::connect();
my $wm = Wily::Message->new(Wily::Message::WMnew, 0, 0, 0, 1,
/tmp/file_to_edit);
$ws->syswrite($wm->flatten());
my $buffer = ;
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMnew: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRnew) {
$win_id = $wm->{window_id};
$wm = Wily::Message->new(Wily::Message::WMattach, $win_id, 0, 0,
Wily::Message::WEdestroy);
$ws->syswrite($wm->flatten());
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMattach: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRattach) {
} else {
die "Expected a WRattach, but didnt get one";
}
} else {
die "Expected a WRnew, but didnt get one";
}
while (1) {
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WEdestroy and $wm->{window_id} == $win_id) {
last;
}
}
A simple object wrapper around Wily messages with a helper function to assist in extracting messages from the wily connection.
Download (0.021MB)
Added: 2007-02-27 License: Perl Artistic License Price:
969 downloads
ebXML::Message 0.03
ebXML::Message is a Perl module to encapsulate an ebMS message. more>>
ebXML::Message is a Perl module to encapsulate an ebMS message.
SYNOPSIS
use ebXML::Message;
# create new message
my $message = ebXML::Message->new
(
CPAId => http://www.you.org/cpa/123456,
Action => NewPurchaseOrder,
MessageId => 12,
RefMessageToId => 11,
Service => ebXML::Message::Service->new
(
VALUE => QuoteToCollect,
Type => myservicetypes,
),
);
# write SOAP XML using DOM
use XML::Xerses;
# DOM Document
my $target = XML::Xerces::StdOutFormatTarget->new();
$writer->writeNode($target,$message->getOutput(DOM-Doc);
# DOM generated / munged XML
print OUT $message->getOutput(DOM-XML);
# use message with SOAP::Lite to call webservice
use SOAP::Lite;
# SOAP::Data::Builder object
my $result = SOAP::Lite->uri(http://uri.to/WebService)
->proxy(http://uri.to/soap.cgi)
->parts($message->getMIMEParts)
->call($message->getOutput(SOAP-Data))
->result;
# SOAP::Data::Builder generated / munged XML
print OUT $message->getOutput(SOAP-XML);
An ebXML message encapsulates all the details of an ebMS message.
ebXML is a mechanism for ensuring reliable delivery of XML-based messages via a transport mechanism such as SOAP. For more details on ebXML, see http://www.ebxml.org/
Large portions of this manual page are copied directly from the ebMS 2.0 specification.
<<lessSYNOPSIS
use ebXML::Message;
# create new message
my $message = ebXML::Message->new
(
CPAId => http://www.you.org/cpa/123456,
Action => NewPurchaseOrder,
MessageId => 12,
RefMessageToId => 11,
Service => ebXML::Message::Service->new
(
VALUE => QuoteToCollect,
Type => myservicetypes,
),
);
# write SOAP XML using DOM
use XML::Xerses;
# DOM Document
my $target = XML::Xerces::StdOutFormatTarget->new();
$writer->writeNode($target,$message->getOutput(DOM-Doc);
# DOM generated / munged XML
print OUT $message->getOutput(DOM-XML);
# use message with SOAP::Lite to call webservice
use SOAP::Lite;
# SOAP::Data::Builder object
my $result = SOAP::Lite->uri(http://uri.to/WebService)
->proxy(http://uri.to/soap.cgi)
->parts($message->getMIMEParts)
->call($message->getOutput(SOAP-Data))
->result;
# SOAP::Data::Builder generated / munged XML
print OUT $message->getOutput(SOAP-XML);
An ebXML message encapsulates all the details of an ebMS message.
ebXML is a mechanism for ensuring reliable delivery of XML-based messages via a transport mechanism such as SOAP. For more details on ebXML, see http://www.ebxml.org/
Large portions of this manual page are copied directly from the ebMS 2.0 specification.
Download (0.014MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1136 downloads
Debug::Message 1.00
Debug::Message is a Perl module that eases the use of debug print with level, indentation and color. more>>
Debug::Message is a Perl module that eases the use of debug print with level, indentation and color.
SYNOPSIS
use Debug::Message;
use Log::Dispatch;
use Log::Dispatch::Screen;
my $dispatcher = Log::Dispatch->new;
$dispatcher->add( Log::Dispatch::Screen->new( name => screen,
min_level => 0 ));
my $info = Debug::Message->new(1);
$info->add_dispatcher($dispatcher);
$info->print("print");
$info->yellow("warn");
$info->red("err");
$info->printcn("error message", bold red);
my $critical = Debug::Message->new(5);
$critical->add_dispatcher($dispatcher);
$critical->redn("err");
For disabling the debugging simply do not attach any dispatchers.
$critical->disable; # Will detach the attached backend
There was no module for simple debug messages supporting debug/verbosity levels and indentation. So this is the one, that is supposed to take this place.
This module is an art of frontend to Log::Dispatch as Log::Dispatch itself supports levels, but no colors and the functions calling is tedious.
There are some methods defined. Each outputs a different color, optionally it can add a newline after the messaage. They dispatch the messages to all added dispatchers, but generaly only one will be needed as the Log::Dispatch itself can have more backends.
<<lessSYNOPSIS
use Debug::Message;
use Log::Dispatch;
use Log::Dispatch::Screen;
my $dispatcher = Log::Dispatch->new;
$dispatcher->add( Log::Dispatch::Screen->new( name => screen,
min_level => 0 ));
my $info = Debug::Message->new(1);
$info->add_dispatcher($dispatcher);
$info->print("print");
$info->yellow("warn");
$info->red("err");
$info->printcn("error message", bold red);
my $critical = Debug::Message->new(5);
$critical->add_dispatcher($dispatcher);
$critical->redn("err");
For disabling the debugging simply do not attach any dispatchers.
$critical->disable; # Will detach the attached backend
There was no module for simple debug messages supporting debug/verbosity levels and indentation. So this is the one, that is supposed to take this place.
This module is an art of frontend to Log::Dispatch as Log::Dispatch itself supports levels, but no colors and the functions calling is tedious.
There are some methods defined. Each outputs a different color, optionally it can add a newline after the messaage. They dispatch the messages to all added dispatchers, but generaly only one will be needed as the Log::Dispatch itself can have more backends.
Download (0.004MB)
Added: 2007-05-01 License: Perl Artistic License Price:
906 downloads
X Message Daemon 0.6.5
X Message Daemon is used to overlay graphical information messages on your X display. more>>
X Message Daemon is used to overlay graphical information messages on your X display.
You can choose parameters such as color, font, icon, and duration.
It also has a frontend Perl daemon and client.
Installing:
# ./configure
# make
# make install
then edit /usr/local/share/Xmsgd/etc/msgmaild.conf and change the configuration to your preferences.
Basic Usage:
- tailing your /var/log/messages :
# tail -f /var/log/messages | msgclient.pl &
<<lessYou can choose parameters such as color, font, icon, and duration.
It also has a frontend Perl daemon and client.
Installing:
# ./configure
# make
# make install
then edit /usr/local/share/Xmsgd/etc/msgmaild.conf and change the configuration to your preferences.
Basic Usage:
- tailing your /var/log/messages :
# tail -f /var/log/messages | msgclient.pl &
Download (MB)
Added: 2006-09-26 License: GPL (GNU General Public License) Price:
1124 downloads
XPA Messaging 2.1.6
XPA Messaging provides seamless communication between Unix programs, including X, Tcl/Tk, and generic select() loops. more>>
XPA Messaging provides seamless communication between Unix programs, including X, Tcl/Tk, and generic select() loops. XPA Messaging provides an easy way for users to communicate with these XPA-enabled programs by executing XPA client commands from a shell.
Because XPA works both at the programming level and the shell level, it is a powerful tool for unifying any environment, offering flexibility in choosing the best level at which to access XPA services.
A program becomes an XPA-enabled server by defining named points of public access through which data and commands can be exchanged with other client programs (and users). Using standard TCP sockets, XPA supports both single-point and broadcast messaging to and from these servers.
Enhancements:
- Ported to Intel icc and gcc 3.3 compilers.
- Upgraded to Tcl/Tk 8.4.
- Support has been added for generating man pages, PDF, and Postscript from the HTML pages.
- Potential buffer overflows in string handling have been fixed.
- There are numerous other bugfixes.
<<lessBecause XPA works both at the programming level and the shell level, it is a powerful tool for unifying any environment, offering flexibility in choosing the best level at which to access XPA services.
A program becomes an XPA-enabled server by defining named points of public access through which data and commands can be exchanged with other client programs (and users). Using standard TCP sockets, XPA supports both single-point and broadcast messaging to and from these servers.
Enhancements:
- Ported to Intel icc and gcc 3.3 compilers.
- Upgraded to Tcl/Tk 8.4.
- Support has been added for generating man pages, PDF, and Postscript from the HTML pages.
- Potential buffer overflows in string handling have been fixed.
- There are numerous other bugfixes.
Download (0.69MB)
Added: 2006-08-03 License: GPL (GNU General Public License) Price:
1177 downloads
Secure Messaging 1.0
Secure Messaging is a Web-based, alternative mail system for sending and receiving messages. more>>
Secure Messaging is a Web-based, alternative mail system for sending and receiving messages.
Use secure messaging to send and receive messages from a alternative web-based mail system. Using the secure messaging system no actual mail is transmitted through any 3rd party servers.
Only an optional message notice is sent to the recepient, the user needs to visit the site in order to read the message.
Normal SMTP mail can hit multiple servers and can possibly be read, stored, or changed anywhere within the process.
Setup secure messaging on an SSL enabled website to enhance the privacy even more.
<<lessUse secure messaging to send and receive messages from a alternative web-based mail system. Using the secure messaging system no actual mail is transmitted through any 3rd party servers.
Only an optional message notice is sent to the recepient, the user needs to visit the site in order to read the message.
Normal SMTP mail can hit multiple servers and can possibly be read, stored, or changed anywhere within the process.
Setup secure messaging on an SSL enabled website to enhance the privacy even more.
Download (0.15MB)
Added: 2005-10-20 License: GPL (GNU General Public License) Price:
1466 downloads
Mail::Message::Body 2.065
Mail::Message::Body is the data of a body in a message. more>>
Mail::Message::Body is the data of a body in a message.
INHERITANCE
Mail::Message::Body has extra code in
Mail::Message::Body::Construct
Mail::Message::Body::Encode
Mail::Message::Body
is a Mail::Reporter
Mail::Message::Body is extended by
Mail::Message::Body::File
Mail::Message::Body::Lines
Mail::Message::Body::Multipart
Mail::Message::Body::Nested
Mail::Message::Body::String
Mail::Message::Body is realized by
Mail::Message::Body::Delayed
SYNOPSIS
my Mail::Message $msg = ...;
my $body = $msg->body;
my @text = $body->lines;
my $text = $body->string;
my IO::Handle $file = $body->file;
$body->print(*FILE);
my $content_type = $body->type;
my $transfer_encoding = $body->transferEncoding;
my $encoded = $body->encode(mime_type => text/html,
charset => us-ascii, transfer_encoding => none);n";
my $decoded = $body->decoded;
The encoding and decoding functionality of a Mail::Message::Body is implemented in the Mail::Message::Body::Encode package. That package is automatically loaded when encoding and decoding of messages needs to take place. Methods to simply build an process body objects are implemented in Mail::Message::Body::Construct.
The body of a message (a Mail::Message object) is stored in one of the many body types. The functionality of each body type is equivalent, but there are performance differences. Each body type has its own documentation with details about its implementation.
<<lessINHERITANCE
Mail::Message::Body has extra code in
Mail::Message::Body::Construct
Mail::Message::Body::Encode
Mail::Message::Body
is a Mail::Reporter
Mail::Message::Body is extended by
Mail::Message::Body::File
Mail::Message::Body::Lines
Mail::Message::Body::Multipart
Mail::Message::Body::Nested
Mail::Message::Body::String
Mail::Message::Body is realized by
Mail::Message::Body::Delayed
SYNOPSIS
my Mail::Message $msg = ...;
my $body = $msg->body;
my @text = $body->lines;
my $text = $body->string;
my IO::Handle $file = $body->file;
$body->print(*FILE);
my $content_type = $body->type;
my $transfer_encoding = $body->transferEncoding;
my $encoded = $body->encode(mime_type => text/html,
charset => us-ascii, transfer_encoding => none);n";
my $decoded = $body->decoded;
The encoding and decoding functionality of a Mail::Message::Body is implemented in the Mail::Message::Body::Encode package. That package is automatically loaded when encoding and decoding of messages needs to take place. Methods to simply build an process body objects are implemented in Mail::Message::Body::Construct.
The body of a message (a Mail::Message object) is stored in one of the many body types. The functionality of each body type is equivalent, but there are performance differences. Each body type has its own documentation with details about its implementation.
Download (0.57MB)
Added: 2006-06-08 License: Perl Artistic License Price:
1233 downloads
THCNET Message System 1.1.0.1
THCNET Message System project is a customizable PHP-enabled Web application. more>>
THCNET Message System project is a customizable PHP-enabled Web application which provides a moderated message system using a backend MySQL database.
Installation
download and install MySQL. download and install apache with mod_rewrite
and php4 or php5 compiled with the pspell libraries.
note: I use MySQL 5.0 and PHP 5.1 in development of THCNET, but it should
work with earlier versions.
do the following
modify the *.template *.css files to make things look how you want
modify the any and all source code as you see fit.
As of release 1.0.pre5 thcnet has an auto-installer/revision control
feature that makes the initial setup much easier.
copy all the files into your htdocs directory on your web server
open index.php in your browser. It will prompt you for values it needs
to perform the installation. Click on setup and it will create the
database for you and populate it.
Now that you have THCNET setup, the first task will be to apply as a new
user. The first user to apply will be given sys-admin rights.
Now you can customize features by clicking on the Admin link to the
left.
Enhancements:
- This release adds the ability to further control the system based on policy maps.
<<lessInstallation
download and install MySQL. download and install apache with mod_rewrite
and php4 or php5 compiled with the pspell libraries.
note: I use MySQL 5.0 and PHP 5.1 in development of THCNET, but it should
work with earlier versions.
do the following
modify the *.template *.css files to make things look how you want
modify the any and all source code as you see fit.
As of release 1.0.pre5 thcnet has an auto-installer/revision control
feature that makes the initial setup much easier.
copy all the files into your htdocs directory on your web server
open index.php in your browser. It will prompt you for values it needs
to perform the installation. Click on setup and it will create the
database for you and populate it.
Now that you have THCNET setup, the first task will be to apply as a new
user. The first user to apply will be given sys-admin rights.
Now you can customize features by clicking on the Admin link to the
left.
Enhancements:
- This release adds the ability to further control the system based on policy maps.
Download (0.37MB)
Added: 2007-06-11 License: GPL (GNU General Public License) Price:
865 downloads
Messa 1.01a (Server)
Messa is an instant messager client and server. more>>
Messa is an instant messager client and server. The client has a curses interface and works on the console.
Messa project supports multilingual messages and private messages. The server supports monoprocess operation (without threads), the ability to choose the listening port, and the ability to run under the console.
<<lessMessa project supports multilingual messages and private messages. The server supports monoprocess operation (without threads), the ability to choose the listening port, and the ability to run under the console.
Download (0.011MB)
Added: 2006-07-21 License: LGPL (GNU Lesser General Public License) Price:
1190 downloads
Mail::Message::Field 2.072
Mail::Message::Field contains one line of a message header. more>>
Mail::Message::Field contains one line of a message header.
INHERITANCE
Mail::Message::Field
is a Mail::Reporter
Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full
SYNOPSIS
my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;
This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.
These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:
my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;
my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;
my $other = $message->get(Reply-To);
<<lessINHERITANCE
Mail::Message::Field
is a Mail::Reporter
Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full
SYNOPSIS
my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;
This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.
These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:
my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;
my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;
my $other = $message->get(Reply-To);
Download (0.58MB)
Added: 2007-07-13 License: Perl Artistic License Price:
833 downloads
Lua Messaging Engine 0.1.0
Lua Messaging Engine is a set of scripts that offer abstract functions for communication via AOLs OSCAR protocol. more>>
Lua Messaging Engine (LuME) is a set of scripts that offer abstract functions for communication via AOLs OSCAR protocol (as used by ICQ and AIM clients), Microsoft Messengers MSNP, and Yahoos YIM protocol. Lua Messaging Engine also includes utility functions for string operations, SHA hashing, and basic HTTPS communication.
An increasing number of software developers are making use of the simplicity and power behind employing a Lua script interface.
Meetroduction, LLC has been using a Lua script interface as a core design concept for the multi protocol messaging component of its proximity based people finder client: Meetro. Beyond that, the interface offers its users a flexible way to vastly extend the clients functionality.
<<lessAn increasing number of software developers are making use of the simplicity and power behind employing a Lua script interface.
Meetroduction, LLC has been using a Lua script interface as a core design concept for the multi protocol messaging component of its proximity based people finder client: Meetro. Beyond that, the interface offers its users a flexible way to vastly extend the clients functionality.
Download (0.089MB)
Added: 2006-01-26 License: MIT/X Consortium License Price:
1368 downloads
Yahoo Messenger 1.0.4
Yahoo! Messenger for UNIX is an instant messenger. more>>
Yahoo! Messenger for Unix sends instant messages to your Windows and Unix friends!
Enhancements:
- Improved Emoticons - Improved Message Archive - Improved sound on RedHat kernels - Yahoo! Address Book integration - File transfer with Windows clients -
<<lessEnhancements:
- Improved Emoticons - Improved Message Archive - Improved sound on RedHat kernels - Yahoo! Address Book integration - File transfer with Windows clients -
Download (0.91MB)
Added: 2005-06-15 License: LGPL (GNU Lesser General Public License) Price:
1171 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 messages 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
