Tony Du’s Blog

So I just installed Google Chrome on my machine at home just to give it a try. My first impression with the browser is fast, fast, fast. This is the fastest browser I’ve ever used. Although I was able to make it crash from watching flash video on youtube and access to a bunch of sites are broken as well (for example, I can’t log-in into my Zimbra web mail client). Overtime, as it becomes more stable, this will be a great browser so Internet Explorer and Mozilla Firefox need to watch out :).

Anyway, try Google Chrome for yourself (no Linux support yet )

Update:
Many people probably notice by now but it seem that Chrome create a new instance for every tab. I tried to use it extensively today instead of Firefox and after while, I see significant slow down on my machine. When I look on my taskmgr and I saw 15 instances of chrome.exe. Urgh! so much for small memory usage. I’ll switch back to firefox for now.

I found this direction from Ubuntu forum but want to have the instruction on my site so that i can quickly reference in the future

sudo apt-get install alien
sudo apt-get install libstdc++5

cd Desktop
mkdir “lexmark z55 - remove me”
cd “lexmark z55 - remove me”
wget http://www.downloaddelivery.com/srfilecache/CJLZ55LE-CUPS-1.0-1.TAR.GZ

tar -xvzf CJLZ55LE-CUPS-1.0-1.TAR.GZ
tail -n +143 lexmarkz55-CUPS-1.0-1.gz.sh > install.tar.gz
tar -xvzf install.tar.gz
sudo alien -t lexmarkz55-CUPS-1.0-1.i386.rpm
sudo alien -t z55llpddk-2.0-2.i386.rpm
sudo tar xvzf z55llpddk-2.0.tgz -C /
sudo tar xvzf lexmarkz55-CUPS-1.0.tgz -C /
sudo ldconfig
cd /usr/share/cups/model
sudo gunzip Lexmark-Z55-lxz55cj-cups.ppd.gz
sudo /etc/rc2.d/S19cupsys restart

Then you’ll have to go and install the driver: menu System -> Administration -> Printers, double-click on the “install printer” icon, select your printer, and at the second step, choose “install driver”. Browse to “/usr/share/cups/model” and select the file “Lexmark-Z55-lxz55cj-cups.ppd”.

Note: The scanner doesn’t work

So for work, i have to write a .Net web service along with an Axis2 client which will consume the web service. One of the requirement for the project is that they have to have the ability to transfer data with each other using MTOM. The whole project/idea seem fun and easy enough. Since I’ve never used/programmed with Axis before, I wanted to start with a very simple web service and client (hello world, echo). After having my environment set up, I went on with the code. I quickly wrote up the web service and client and everything worked as expected. I then moved on to MTOM portion of the code. I changed the web service to a simple file transfer service (download/upload) using MTOM (WSE3). Then, i wrote up the client portion of the code. Things seemed to go very smoothly but when I tried to test the code, I kept on getting 400: Bad Request response and Axis Fault exception from my client code. Thinking that i probably made a mistake in my code, I went through the code again and again. However, i can’t see what cause the issue. Google search on the exception and it seemd that some people also has similar issue/exception so i tried to use their method to debug:

- Use TCPMON/HTTPAnalyzer to check the header and content of the SOAP message : everything is good! (checked)
- Client stub are generated using WSDL2JAVA using :
+ XMLBeans (checked)
+ADB (checked)
- Create the SOAP message using AXIOM and (checked)

The issue was still there and I still didn’t know what the heck was wrong. So then I was thinking that probably something wrong with my .NET web service. I decided to write a C# client instead. However, with the C# client, everything worked perfectly. I was able to transfer (upload/download files) to/from the web service. The whole day went by and i still didn’t know what was wrong and how to fix it.

The next day, I took a look again at the SOAP message header and compare them between C# client and AXIS2 Java client. By then, I noticed that the “start” attribute for the java client doesn’t match with the “content-id” and it’s also missing a “<” . So on to the Google search “.NET web service, AXIS2, MTOM, start missing <” and the first search result lead me to this link which then lead me to this AXIS2 1.3 BUG 3196. Follow the solution, i replace the Axiom-api jar with the latest one and everything work as expected.

I don’t understand how this issue was found and fixed in early Oct, 2007 and the fixed is still not in the distributed zip file on Axis website. If it was updated, it would save me and probably many others who are new to AXIS/AXIS2 a lot of trouble debug and research for solution.

After another re-org in Microsoft, my test features ownership areas have now change to:

- Input
- Raw Input Thread (RIT)
- Messages from input, and queue management
- Desktop Thread
- UIPI (User Interface Privilege Isolation)
- AppInit_DLLs
- Caret
- HotKey

These areas seem pretty interesting although some of them is completely new to me. Seem like i’ll have to start educate myself a little more.

I found this little hack after reading a Digg article. The real link to the tutorial video is at metacafe. All i do here is take those information and put it here on my webpage so i can reference it later quickly.
Anyway, by default, internet browser such as IE and Firefox are optimized for dial-up connection. This hack increase the simultaneous connections per page for faster browsing

For IE:
1) Go to Start -> Run
2) Type “regedit”
3) Go to HKEY_CURRENT_USER -> Software -> Microsoft -> Windows -> CurrentVersion -> Internet Settings
4) Check to see if you have “MaxConnections Per1_0Server” and “MaxConnections PerServer” registry key
5) If you have those key listed then right click on them -> modify -> Change value to 10 (decimal). If you dont have these key listed then right click -> new -> DWORD values -> name them “MaxConnections Per1_0Server” and “MaxConnections PerServer” respectively and assign both with value 10 (decimal)

6) Close registry editior and try using IE, u’ll see significant improvement

For Firefox

1) On address bar type “about:config”
2) on filter type “network”
3) Scroll down and look for “network.http.pipelining”
4) If it’s already set to “true” then you’re good, otherwise double click on it and set it to true
5) Look for “network.http.pipelining.maxrequests”
6) Double click on it and set the value to 8. (Note: this is different from the turtorial i read. In the tutorial, he said to set the value to 10. However, firefox can only handle 8 pipeline so there’s no reason to set it above that. This info is from mozilla knowlegde base site)
7) on filter type “nglayout”
Look for “nglayout.initialpaint.delay” and set the value to 0 (This value is the amount of time (ms) the browser waits before it acts on information it recieves. The default value is 750 ms, which means Firefox waits about 1 sec before receiving the data and drawing it on screen)
9) Again, if you can’t find this string then right click -> new -> string -> name it “nglayout.initialpaint.delay” and set the value to 0.
10) Now use your Firefox and you should see some improvement.

Happy surfing!