Home > Articles > Home & Office Computing > The Web/Virtual Worlds/Social Networking

Like this article? We recommend

Like this article? We recommend

The NowPlayingServlet

The HTTP Post processing logic of your setup lies in NowPlayingServlet.java, which you can download in the Web Application Archive (WAR) associated with this article here. I suggest that you take some time to analyze the code before moving on. Don't worry, though—I'll dissect the code piece by piece. For simplicity, I process only the title and the artist of the current song; the procedure for processing other current song information and previously played song information will be obvious once you've seen this example.

To store information about the songs in the servlet, I use local variables that are created at the first invocation of the servlet:

String currentSong = "";
String artist = "";

The Now Playing Plug-in invokes the doPost method when it performs an HTTP Post. The doPost method of the servlet, shown below, extracts the title and artist of the current song playing, as informed by the Now Playing Plug-in through HTTP Post parameters, which you get using a getParameter call from your HttpServletRequest object.

public void doPost(
  HttpServletRequest req,
  HttpServletResponse resp)
  throws ServletException, IOException
{
currentSongTitle =
    req.getParameter("Title1");
  currentSongArtist =
    req.getParameter("Artist1");
  System.out.println(
      "New Track Discovered: "
      + currentSongTitle
      + " by "
      + currentSongArtist);
}

Notice that I pulled the request parameters Title1 and Artist1. If you wanted to access the history of songs played, you could change the number of the request parameter. For example, Title2 would get you the title of the song that was last played, and Artist3 would get you the artist name of the song that was played two songs ago. I went ahead and used a System.out call for troubleshooting purposes so you can analyze your server logs to see if the Now Playing Plug-In is truly posting to the NowPlayingServlet.

The remaining part of the NowPlayingServlet is the doGet method:

public void doGet(
  HttpServletRequest req,
  HttpServletResponse res)
  throws ServletException, IOException
{
  res.setContentType("text/html");
  PrintWriter out =
    res.getWriter();
  out.println("<html>");
  out.println(
  "<META HTTP-EQUIV='Refresh' CONTENT='3;[ccc]
URL=http://localhost:9080/WinampProject/NowPlayingServlet'>");
  out.println("<body>");
  out.println("Now Playing: ");
  out.println(currentSongTitle);
  out.println(" by: " + currentSongArtist);
  out.println("</body></html>");
  out.close();
}

Whereas the Winamp NowPlayingServlet posts to the NowPlayingServlet that ends up calling the doPost method, visitors of your website will invoke the NowPlayingServlet's doGet method, which will report to them information about the current song playing via an HTTP response. The code above creates an HTML response that is sent back to the client, reporting the current song title as well as current song's artist information.

Notice the META HTTP-EQUIV='REFRESH' call to the URL http://localhost:9080/WinampProject/NowPlayingServlet. This URL must be modified in your code to point to the eventual endpoint of your servlet. Of course, for the outside world to see the servlet, the localhost would have to be replaced with your domain name/IP address. This META tag is used so that a client visiting your website can have his browser automatically refresh after a period of 3 seconds. Of course, you can change this value to meet your preference.

In addition to the NowPlayingServlet, my Now Playing setup requires a couple auxiliary HTML files. One of them is the HTML file that clients will access via their browser. I have included this in the project zip file as index.html. The code of the HTML file is shown below:

<FRAMESET BORDER=0 ROWS="50,*">
 <FRAME SRC="http://localhost:9080/WinampProject/NowPlayingServlet" [ccc]
NAME="nowPlayingFrame" BORDER=0 SCROLLING=0>
 <FRAME SRC="http://localhost:9080/WinampProject/content.html" [ccc]
NAME="contentFrame" BORDER=0 SCROLLING=0>
</FRAMESET> 

Notice that the HTML file contains a couple of frames. One of the frames points to the NowPlayingServlet. As before, you will need to change the URL of the servlet to correspond to the external URL of your servlet as the outside world will know it.

The second frame points to an HTML file named content.html, which, in short, is there only to show you where you can place your web content. The code of content.html is shown below:

<HTML>
<HEAD>
<TITLE>content.html</TITLE>
</HEAD>
<BODY>
<HR SIZE=1>
<P>My page content would go here.</P>
</BODY>
</HTML>

The beauty of our framed setup allows for the frame named nowPlayingFrame to be updated every 3 seconds, as mandated by the META refresh tag we planted in the servlet's HTML output.

When you have the NowPlayingServlet deployed and two HTML files deployed to your servlet container and visible to the outside world, you are ready to test things.

After deploying to the web server, you should see communication between the plug-in and the NowPlayingServlet. When a song stops playing in Winamp and the next song is loaded from a playlist, you should see a small pop-up like the one in Figure 5.

Figure 5

Figure 5 The Now Playing Plug-in posting information.

If you set things up properly, you should see a message in your web server's console stating that a new track was discovered after each song in your playlist ends (see Figure 6).

Figure 6

Figure 6 Analyzing your console for new track discovery by the NowPlaying servlet.

At this point, you are ready to let your clients view your work. Your web visitors simply need to visit the index.html page on your web application server. In Figure 7, the page http://localhost:9080/WinampProject/index.html is being visited. Of course, this URL will need to be updated with external URL of the index.html page. The client browser will call the NowPlaying servlet every 3 seconds to keep up-to-date with what the Winamp player is playing.

Figure 7

Figure 7 Client browser updated with track information.

Now you can use the Now Playing Plug-In to produce HTTP posts that can be consumed by a servlet container. The information contained in the payload of the HTTP Post contains information such as the title and artist of the current track playing, as well as previous tracks that have played. You can access a plethora of other information from the HTTP Post payloads of the Now Playing Plug-in. To learn more, see http://www.cc.jyu.fi/~ltnevala/nowplaying/instruction.html#post.

You can use the knowledge you gained in this article in tandem with my Winamp streaming article to let your website visitors keep up with what song you are currently playing on your Winamp-based Internet broadcast.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020