Sunday, August 24, 2008
KingFisher Airlines, Indias most colorful and luxurious domestic airlines provides Entertainment system which are based on Linux.
It so happened that I was travelling from Hyderabad to Bangalore in KingFisher flight. 5 min before the take off , all the entertainment units got restarted. I was totally amazed when I saw a Linux boot sequence getting displayed on the screens. It was an embedded Linux ( a scale down and customized Linux especially for the Embedded Systems). After the booting was over the X window console came and then suddenly the moving map. The entire thing was very exciting. I wanted to share this information at that time itself. I sent SMSes to my friend who is a Linux Junnkie. I wanted to send this information to everybody who can get excited like me. For the first time I realized the use of microblogs like twitter. Had I got a twitter account on mobile I could have immediately posted the information on my twitter widget on the Blog. So the flight seem to be providing me lot of insights....
For all the Linux junkies KingFisher is a nice example of proving the use of it in the commercial systems.
Saturday, August 2, 2008
Cracking an interview is what most of the people look forward. People generally prepare a lot for an interview in terms of their technical stuff, personal questions etc. All this is fine but I think even the interviewer is aware of all these preparations the candidate usually do, so he might not be very impressed if you answer him in the artificially imposed sophisticated looks and manners. The interviewer has 1 min to judge you and you have to take the lead in that 1 min. I have recently given 4-5 interviews (just for fun) and in all those interviews I found that no body is actually interested in looking at you "artificial manners". They will be more than happy if you remain what you actually are. So here is the trick and this is applicable for both freshers and the experienced people.
Just to put it in simple sentences
1. Prepare slides or some visual depiction of the work you have done so far.
2. Ask the interviewer permission to show your stuff.
3. In all probability he will say yes
4. Using your slides/ graphs give an overview of the work
5. Be very casual while describing. The words should be just oozing out of the mouth.
6. You should look proud and confident of what you have done. Think as if you are selling your work to a customer
7. You should tell what impact you work has put in the current company (if you are switching the job) or if you are fresher than how your work has been judged by the college
8. All this has a great effect on the interviewer.
- He thinks that you are confident about what you have done--so you are not telling a lie.
- He thinks that you are sound in the area that you are looking for.
- He understands that you can express yourself---a very important quality
- He understands that you can sell your case ---If you cannot market a thing then what is the use to produce it?
- He thinks that you are professional-- slides, graphs, if permitted a prototype
"BE COOL AND TALK RATHER THAN LISTEN AND GET TENSE"
My take on REST and SOAP
- Soap supports more RPC style of architecture where the use of SOAP is to invoke a remote function carrying in the message the function name and the various parameters. The RPC is basically a function that is sitting on a remote machine.
- The function has a specified number of parameters that needs to be provided to make use of the function. The use of SOAP is to make requests to such functions and to get the response back.
- SOAP uses XML to transfer the data and so it is heavy in size.
- The SOAP message is cryptic in the sense that it contains a header that wil specify the route, the info about the message and sometimes the security aspect for the message
- The SOAP message is difficult to create without the tools. So these days the langusgaes provide the library functions which will create the SOAP message
- The SOAP is generally sent using HTTP but other protocols are also valid like Java Message service
- SOAP is very function (verb ) centric. The way you get the things done is by calling a function so to get the stock prices you will call a function (web method: A webservice will have number of methods) getstock(GE)
Now the function will calculate the price and send it back to you
You must know the names of the function and the way it is going to use the parameters. For that you need to get the WSDL file which is very cryptic.
- SOAP syntax is not user friendly and human readable
- When SOAP makes the http request its difficult to find out which http method it is actually going to use.
In case of rest the functions are fixed it will be get, put, post and delete. You will mention the name of the stock directly while making the request (each object will have a different URI) so www.stockprice/category/stock/GE
In this case the description of how to make the call is very simple and its intuitive.
No extra tool is required, The call is very simple.
REST is only for http since it uses the protocols methods GET, PUT(Update), POST (create), DELETE. This is good since the user don’t have to find out which method will be used for a specific purpose. Its basically service_name/noun so Stock is a service and GE is the noun