94 text messages

(CBS News) Teens are sending more text messages than ever before, according to a new report called “Teens, Smartphones & Texting” conducted by the Pew Internet & American Life Project. According to Pew Internet, teens are sending an average of 60 text messages per day.

27 trillion texts

200 thousand SMS

Yes, when my friends can’t answer my phone, I will text him to let him know and wait for his reply. I believe when the person answering the phone is having a conference or in a cinema, it’s better to text him instead of having a telephone call.

The Most Common Text Messages

• “I love you” is texted an average of 1,186 times a year.
• “When will you be home?” is texted an average of 1,018 times.
• “Where are you?” is texted an average of 989 times.

Primary Message Is Not the Whole Message

• Primary messages refer to the intentional content, both verbal and nonverbal.
• Secondary messages refer to the unintentional content, both verbal and nonverbal.
• Auxiliary messages refer to the intentional and unintentional ways a primary message is communicated.

It can take anywhere from a few seconds to a few minutes for a text message to get to a recipient unless the phone is off or out of range. The majority of messages are instant, but in some rare cases, sending can take a little longer.

Types of Messaging

• Email. When it comes to messaging, email is the killer application.
• Paging. One of the earliest forms of messaging to mobile devices was paging.
• Short Message Service (SMS)
• Enhanced Message Service (EMS)
• Multimedia Message Service (MMS)
• Instant Messaging.
• HDML Notifications.

There are four main types of communication we use on a daily basis: verbal, nonverbal, written and visual.

There are three types of messages: Nominal, Expressive and Predicative.

In client-server protocols, like HTTP, sessions consist of three phases: The client sends its request, and waits for the answer. The server processes the request, sending back its answer, providing a status code and appropriate data.

After receiving and interpreting a request message, a server responds with an HTTP response message: A Status-line. Zero or more header (General|Response|Entity) fields followed by CRLF. An empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header fields.

To get the response body as a string we can use the EntityUtils. toString() method. This method read the content of an HttpEntity object content and return it as a string. The content will be converted using the character set from the entity object.

Any response message which “MUST NOT” include a message-body (such as the 1xx, 204, and 304 responses and any response to a HEAD request) is always terminated by the first empty line after the header fields, regardless of the entity-header fields present in the message.

GET requests don’t have a request body, so all parameters must appear in the URL or in a header. While the HTTP standard doesn’t define a limit for how long URLs or headers can be, mostHTTP clients and servers have a practical limit somewhere between 2 kB and 8 kB.

HTTP messages are how data is exchanged between a server and a client. There are two types of messages: requests sent by the client to trigger an action on the server, and responses, the answer from the server.

An HTTP response is also divided into three parts: Status line, header and body.

The request/response cycle traces how a user’s request flows through the app. Understanding the request/response cycle is helpful to figure out which files to edit when developing an app (and where to look when things aren’t working).

Both GET and POST method is used to transfer data from client to server in HTTP protocol but Main difference between POST and GET method is that GET carries request parameter appended in URL string while POST carries request parameter in message body which makes it more secure way of transferring data from client to …

GET is used for viewing something, without changing it, while POST is used for changing something. For example, a search page should use GET to get data while a form that changes your password should use POST . Essentially GET is used to retrieve remote data, and POST is used to insert/update remote data.

PUT method is call when you have to modify a single resource, which is already a part of resource collection. POST method is call when you have to add a child resource under resources collection. RFC-2616 depicts that the PUT method sends a request for an enclosed entity stored in the supplied request URI.

GET is slightly faster because the values are sent in the header unlike the POST the values are sent in the request body, in the format that the content type specifies.

Yes, you can send a request body with GET but it should not have any meaning.

POST means “create new” as in “Here is the input for creating a user, create it for me”. PUT means “insert, replace if already exists” as in “Here is the data for user 5”. You POST to example.com/users since you don’t know the URL of the user yet, you want the server to create it.

In summary, POST does not require a body.

When the POST request is sent via a method other than an HTML form — like via an XMLHttpRequest — the body can take any type….POST.

Request has body	Yes
Idempotent	No
Cacheable	Only if freshness information is included
Allowed in HTML forms	Yes

In computing, POST is a request method supported by HTTP used by the World Wide Web. By design, the POST request method requests that a web server accepts the data enclosed in the body of the request message, most likely for storing it. It is often used when uploading a file or when submitting a completed web form.

Post Request in Postman

1. Now let us add a Request Body to our POST request.
2. Click on raw and select format type as JSON, since we have to send in correct format which the server expects.
3. This endpoint expects a Json body which contains the details of the new user.
4. Press Send and see the Response Body and Response Status.