Tech Talk Insights

J2ME Security Architecture is driven from Java Sandbox Architecture . J2ME represents two level of securities:- Low Level KVM Security Application Level Security Low Level KVM Security is divided into two steps: Pre-verification performs certain checks on the Java bytecodes using preverify tool, if first level of verification is passed, then preverifier add special stack map attributes into class files to facilitate runtime in-device verification. Note that preverified class files with the special attribute are approximately 5% larger than the original files. In-device verification is performed on real device by KVM. It refers to the additional information attached to the pre-verified files & verify whether the class file is structurally or conceptually correct according to J2ME specifications. As you know small devices are memory constraints, so split verifier improves verification process by generating annotations at compile time and then using this informat...

Hi Readers, Again while working on my blog, I found that some one of you are looking for an article on "Block a Call". But I am not clear about the stuff that you are looking for using J2ME or for some other technologies. No issues, I'll try to explain about it. AFAIK, You can not block a call or SMSs using J2ME APIs. Because MIDlet can only execute within "Sandbox". Now if you are trying to support this kind of functionality in your application, then you need to know about the market segment and the device penetration ratio in that market. So that you can build your app using different technologies. Let me give you more brief idea about it using an example:- Suppose we are targeting XYZ market and the device penetration ratio is as following for that market segment:- Nokia S60 & other Symbian  devices - 45% Nokia S40  & other Java devices - 30% Android, iPhone, Blackberry  & other devices - 25% So now, you can target first 45% devices using th...