version 1.56, 2003/06/23 22:25:14
|
version 1.58, 2003/07/25 01:18:04
|
Line 44
|
Line 44
|
# |
# |
package Apache::lonmsg; |
package Apache::lonmsg; |
|
|
|
=pod |
|
|
|
=head1 NAME |
|
|
|
Apache::lonmsg: supports internal messaging |
|
|
|
=head1 SYNOPSIS |
|
|
|
lonmsg provides routines for sending messages, receiving messages, and |
|
a handler to allow users to read, send, and delete messages. |
|
|
|
=head1 OVERVIEW |
|
|
|
=head2 Messaging Overview |
|
|
|
X<messages>LON-CAPA provides an internal messaging system similar to |
|
email, but customized for LON-CAPA's usage. LON-CAPA implements its |
|
own messaging system, rather then building on top of email, because of |
|
the features LON-CAPA messages can offer that conventional e-mail can |
|
not: |
|
|
|
=over 4 |
|
|
|
=item * B<Critical messages>: A message the recipient B<must> |
|
acknowlegde receipt of before they are allowed to continue using the |
|
system, preventing a user from claiming they never got a message |
|
|
|
=item * B<Receipts>: LON-CAPA can reliably send reciepts informing the |
|
sender that it has been read; again, useful for preventing students |
|
from claiming they did not see a message. (While conventional e-mail |
|
has some reciept support, it's sporadic, e-mail client-specific, and |
|
generally the receiver can opt to not send one, making it useless in |
|
this case.) |
|
|
|
=item * B<Context>: LON-CAPA knows about the sender, such as where |
|
they are in a course. When a student mails an instructor asking for |
|
help on the problem, the instructor receives not just the student's |
|
question, but all submissions the student has made up to that point, |
|
the user's rendering of the problem, and the complete view the student |
|
saw of the resource, including discussion up to that point. Finally, |
|
the instructor is reading all of this inside of LON-CAPA, not their |
|
email program, so they have full access to LON-CAPA's grading |
|
interface, or other features they may wish to use in response to the |
|
student's query. |
|
|
|
=back |
|
|
|
Users can ask LON-CAPA to forward messages to conventional e-mail |
|
addresses on their B<PREF> screen, but generally, LON-CAPA messages |
|
are much more useful then traditional email can be made to be, even |
|
with HTML support. |
|
|
|
Right now, this document will cover just how to send a message, since |
|
it is likely you will not need to programmatically read messages, |
|
since lonmsg already implements that functionality. |
|
|
|
=head1 FUNCTIONS |
|
|
|
=over 4 |
|
|
|
=cut |
|
|
use strict; |
use strict; |
use Apache::lonnet(); |
use Apache::lonnet(); |
use vars qw($msgcount); |
use vars qw($msgcount); |
Line 192 sub newmail {
|
Line 254 sub newmail {
|
|
|
# =============================== Automated message to the author of a resource |
# =============================== Automated message to the author of a resource |
|
|
|
=pod |
|
|
|
=item * B<author_res_msg($filename, $message)>: Sends message $message to the owner |
|
of the resource with the URI $filename. |
|
|
|
=cut |
|
|
sub author_res_msg { |
sub author_res_msg { |
my ($filename,$message)=@_; |
my ($filename,$message)=@_; |
unless ($message) { return 'empty'; } |
unless ($message) { return 'empty'; } |
Line 255 sub user_crit_msg_raw {
|
Line 324 sub user_crit_msg_raw {
|
|
|
# New routine that respects "forward" and calls old routine |
# New routine that respects "forward" and calls old routine |
|
|
|
=pod |
|
|
|
=item * B<user_crit_msg($user, $domain, $subject, $message, $sendback)>: Sends |
|
a critical message $message to the $user at $domain. If $sendback is true, |
|
a reciept will be sent to the current user when $user recieves the message. |
|
|
|
=cut |
|
|
sub user_crit_msg { |
sub user_crit_msg { |
my ($user,$domain,$subject,$message,$sendback)=@_; |
my ($user,$domain,$subject,$message,$sendback)=@_; |
my $status=''; |
my $status=''; |
Line 335 sub user_normal_msg_raw {
|
Line 412 sub user_normal_msg_raw {
|
|
|
# New routine that respects "forward" and calls old routine |
# New routine that respects "forward" and calls old routine |
|
|
|
=pod |
|
|
|
=item * B<user_normal_msg($user, $domain, $subject, $message, |
|
$citation, $baseurl, $attachmenturl)>: Sends a message to the |
|
$user at $domain, with subject $subject and message $message. |
|
|
|
=cut |
|
|
sub user_normal_msg { |
sub user_normal_msg { |
my ($user,$domain,$subject,$message,$citation,$baseurl,$attachmenturl)=@_; |
my ($user,$domain,$subject,$message,$citation,$baseurl,$attachmenturl)=@_; |
my $status=''; |
my $status=''; |
Line 486 sub comprep {
|
Line 571 sub comprep {
|
$quotemsg=~s/\r/\n/g; |
$quotemsg=~s/\r/\n/g; |
$quotemsg=~s/\f/\n/g; |
$quotemsg=~s/\f/\n/g; |
$quotemsg=~s/\n+/\n\> /g; |
$quotemsg=~s/\n+/\n\> /g; |
|
my $torepl=&Apache::loncommon::aboutmewrapper( |
|
&Apache::loncommon::plainname($content{'sendername'},$content{'senderdomain'}),$content{'sendername'},$content{'senderdomain'}).' ('. |
|
$content{'sendername'}.'@'. |
|
$content{'senderdomain'}.')'; |
my $subject='Re: '.$content{'subject'}; |
my $subject='Re: '.$content{'subject'}; |
my $dispcrit=''; |
my $dispcrit=''; |
if (&Apache::lonnet::allowed('srm',$ENV{'request.course.id'})) { |
if (&Apache::lonnet::allowed('srm',$ENV{'request.course.id'})) { |
Line 499 sub comprep {
|
Line 588 sub comprep {
|
$r->print(<<"ENDREPLY"); |
$r->print(<<"ENDREPLY"); |
<form action="/adm/email" method=post> |
<form action="/adm/email" method=post> |
<input type=hidden name=sendreply value="$msgid"> |
<input type=hidden name=sendreply value="$msgid"> |
|
To: $torepl<br /> |
Subject: <input type=text size=50 name=subject value="$subject"><p> |
Subject: <input type=text size=50 name=subject value="$subject"><p> |
<textarea name=message cols=84 rows=10 wrap=hard> |
<textarea name=message cols=84 rows=10 wrap=hard> |
$quotemsg |
$quotemsg |
Line 965 BEGIN {
|
Line 1055 BEGIN {
|
$msgcount=0; |
$msgcount=0; |
} |
} |
|
|
|
=pod |
|
|
|
=back |
|
|
|
=end |
|
|
1; |
1; |
__END__ |
__END__ |
|
|