"Message Boxes" Please respond to the following:

Computer Science
Tutor: None Selected Time limit: 1 Day

There are three different types of messages:information,warning,and critical messages.Imagine that your program has a problem reading the CD or DVD.Determine the type of message that should be displayed.Provide a sample of the content of the message

May 10th, 2015

n many user-to-user message exchange systems, message senders often
   wish to know if the human recipient actually received a message or
   has the message displayed.

   Electronic mail [RFC5321] offers a solution to this need with Message
   Disposition Notifications [RFC3798].  After the recipient views the
   message, her mail user agent generates a Message Disposition
   Notification, or MDN.  The MDN is an email that follows the format
   prescribed by RFC 3798 [RFC3798].  The fixed format ensures that an
   automaton can process the message.

   The Common Presence and Instant Messaging (CPIM) format, Message/CPIM
   [RFC3862], is a message format used to generate instant messages.
   The Session Initiation Protocol (SIP [RFC3261]) can carry instant
   messages generated using message/CPIM in SIP MESSAGE requests

   This document extends the Message/CPIM message format in much the
   same way Message Disposition Notifications extends electronic mail.
   This extension enables Instant Message Senders to request, create,
   and send Instant Message Disposition Notifications (IMDN).  This
   mechanism works for page-mode as well as session-mode instant
   messages.  This document only discusses page-mode.  Session-mode is
   left for future standardisation efforts.
his specification defines three categories of disposition types:
   "delivery", "processing", and "display".  Specific disposition types
   provide more detailed information.  For example, the "delivery"
   category includes "delivered" to indicate successful delivery and
   "failed" to indicate failure in delivery.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. This document refers generically to the sender of a message in the masculine (he/him/his) and the recipient of the message in the feminine (she/her/hers). This convention is purely for convenience and makes no assumption about the gender of a message sender or recipient.

3. Terminology

o IM: An Instant Message generated using the Message/CPIM format. o IMDN: An Instant Message Disposition Notification generated using the Message/CPIM format that carries an IMDN XML document. o Message: An IM or an IMDN generated using the Message/CPIM format. o IM Sender: An endpoint (user agent) generating and sending an IM. Also, the endpoint request IMDNs for an IM. Quite often, the IM Sender is the IMDN Recipient. However, that is not always the case, since the IMDN uses the From header in the CPIM message. That value is often the IM Sender's Address of Record (AOR). This address may in fact resolve to different user agents. o IM Recipient: An endpoint (user agent) that receives IMs. The IM Recipient, as the node that presumably renders the IM to the user, generates and sends delivery IMDNs to IMs, if requested by the IM Sender and allowed by the IM Recipient. o Endpoint: An IM Sender or an IM Recipient. o Intermediary: An entity in the network, most often an application server (including URI-List and store-and-forward servers), that forwards an IM to its final destination. Intermediaries also can generate and send processing IMDNs to IMs, if requested by the IM Sender and allowed by policy.

May 10th, 2015

Did you know? You can earn $20 for every friend you invite to Studypool!
Click here to
Refer a Friend
May 10th, 2015
May 10th, 2015
Mar 29th, 2017
Mark as Final Answer
Unmark as Final Answer
Final Answer

Secure Information

Content will be erased after question is completed.

Final Answer