Skip to main content

More Bad News for Yahoo in Mobile Markets

Good news is hard to come by for Yahoo these days. South is the direction for company's search market share, advertising revenue and stock prices. As its future remains shrouded in uncertainty, a number of good engineers have left Yahoo for Google.

No soap Opera for Yahoo!
The recent spate of bad news is from mobile market where Opera has recently replaced Yahoo! One search with Google search. Yahoo! One search had been the default search engine in Opera Mini browser for handsets. It used to show the search results from web, mobile web and image search in the first search result page and users could choose their required search category after that. Google too gives you option of Mobile or Classic version of search page.


Nokia-Google Alliance
Nokia mobile phones come preloaded with Yahoo! Go, a software suite for mobile devices. But now Nokia too has announced that they are collaborating with Google. As a consolation T-Mobile has signed up Yahoo for providing search to their customers but with Google present on world's largest selling mobile phones it's highly unlikely that customers will goto network provider's portal to access search engine. However Yahoo may hope some eye balls on non-Nokia handsets having T-Mobile connection!

These two are major jolts for Yahoo and it will take some serious fire fighting by Jerry Yang and his team to avoid more serious damages.

Comments

Popular posts from this blog

File upload problem: UTF-8 encoding not honored when form has multipart/form-data

The problem that I was facing was something like this. I was using Apache Commons File Upload library to upload and download some file.

I had a form in which user can upload a file and another field 'name' in which she can give any name to the file being loaded.


When I submitted the form, the file was uploaded fine but the value in name field was garbled. I followed all the possible suggestions I found:

<%@page pageEncoding="UTF-8"%> set. <%@page contentType="text/html;charset=UTF-8"%gt; set after the first directive. <meta equiv="Content-Type" content="text/html;charset=UTF-8"> in the head. enctype="multipart/form-data" attribute in the form. accept-charset="UTF-8" attribute in the form.
in the Servlet:
before doing any operations on request object: request.setCharacterEncoding("UTF-8"); For accessing the value

FileItem item = (FileItem) iter.next();

if (item.isFormField()) {

//For regular…

java.lang.IllegalArgumentException: Malformed \uxxxx encoding

I was getting this exception during build while running ant. Googling didn't help much and I was flummoxed because the same code was running fine till now.

My code reads a text file and does some operations on the basis of values read. It was only when I saw the text files I understood the error. I had copied the text in wordpad and saved it as .txt file. Wordpad had put lot of formatting information before and after the content. Also there was "\par" after every line, which was giving this error.

So moral of the story: if you get this exception check your properties file (or any other file that your code might be reading.)

Easiest way to print Timestamp in Java

Rather than using Calendar.getTime() we can use java.sql.Timestamp class to get the time stamp which gives date and time till millisecond precision.

System.out.println(new Timestamp(System.currentTimeMillis()));

Above will give you current timestamp in this format: 2010-07-27 16:37:45.39