Saturday 26 August 2017

Privacy Policy

Privacy Policy

built the I Am Rich! I can Buy Anything app as a Commercial app. This SERVICE is provided by and is intended for use as is.
This page is used to inform website visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service.
If you choose to use my Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that I collect is used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy.
The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which is accessible at I Am Rich! I can Buy Anything unless otherwise defined in this Privacy Policy.
Information Collection and Use
For a better experience, while using our Service, I may require you to provide us with certain personally identifiable information, including but not limited to This page is used to inform website visitors regarding my policies if anyone decided to use Service, this app uses android.permission.READ_PHONE_STATE.. The information that I request is retained on your device and is not collected by me in any way
The app does use third party services that may collect information used to identify you.
Link to privacy policy of third party service providers used by the app
Log Data
I want to inform you that whenever you use my Service, in a case of an error in the app I collect data and information (through third party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing my Service, the time and date of your use of the Service, and other statistics.
Cookies
Cookies are files with small amount of data that is commonly used an anonymous unique identifier. These are sent to your browser from the website that you visit and are stored on your device internal memory.
This Service does not use these “cookies” explicitly. However, the app may use third party code and libraries that use “cookies” to collection information and to improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service.
Service Providers
I may employ third-party companies and individuals due to the following reasons:
  • To facilitate our Service;
  • To provide the Service on our behalf;
  • To perform Service-related services; or
  • To assist us in analyzing how our Service is used.
I want to inform users of this Service that these third parties have access to your Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose.
Security
I value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and I cannot guarantee its absolute security.
Links to Other Sites
This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by me. Therefore, I strongly advise you to review the Privacy Policy of these websites. I have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.
Children’s Privacy
These Services do not address anyone under the age of 13. I do not knowingly collect personally identifiable information from children under 13. In the case I discover that a child under 13 has provided me with personal information, I immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact me so that I will be able to do necessary actions.
Changes to This Privacy Policy
I may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. I will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately after they are posted on this page.
Contact Us
If you have any questions or suggestions about my Privacy Policy, do not hesitate to contact me.

Monday 9 July 2012

Points to Remember


                                                  Points To Remember for SCJP


The datatype in a switch statement must be convertible to int, i.e., only byte, short, char and int
can be used in a switch statement, and the range of the datatype used must cover all of the cases
(case statements).
An integer literal (w/o a decimal pt) is assumed to be a 32-bit int primitive, but a value containing
a decimal point is assumed to be a 64-bit double.
Wrapper classes for primitives produce immutable objects.

• Java characters are 16-bit unicode characters, and they can be initialized in the following ways:
o char c1 = '\u0057'
o char c1 = 'w'
o char c1 = 87
o char c1 = (char) 87 (acc to RHE)
o char c1 = '\r'

• instanceof operator can take a class, an interface or an array type as an argument.
• To test if an object is an array, use: myObject.getClass().isArray();
• MenuContainer interface is implemented by Container, Frame, Menu and MenuBar
• An identifier must begin with a letter, a dollar sign ($), or an underscore. Subsequent characters
maybe letters, $, underscore, or digits, but NOT other characters liek %, &, etc.
• The keywords syncrhonized, private and protected cannot be used with a class.
• A variable declared inside a try block cannot be used in the catch block.
• If no super-class constructor is explicitly called, and there is no call to other constructor (using
this(..)), the default constructor of the superclass (w/o any arguments) is automatically called.
• wait(), notify() and notifyAll() are the instance methods of Object class, not Thread class (but they
are inherited by Thread class).
• stop(), suspend() and resume() are deprecated methods in Java 1.2
• References to member methods are resolved at runtime using the type of object, but the references
to member variables are computed at compile time using the type of the reference.
• Javadoc documentation does not list private variables and methods.
• A valid overload differs in teh number or types of arguments. Difference is return type only is not
a valid overload.
• Inner classes defined local to a block may not be declared to be static.
• Member inner classes cannot have the same name as enclosing class, but they CAN subclass the
enclosing class.

Basic Instructions


                                                  


What are the potential trips/traps in SCJP exam?
• Two public classes in the same file.
• Main method calling a non-static method.
• Methods with the same name as the constructor(s).
• Thread initiation with classes that don’t have a run() method.
• Local inner classes trying to access non-final vars.
• Case statements with values out of permissible range.
• Math class being an option for immutable classes !!
• instanceOf is not same as instanceof
• Private constructors
• An assignment statement which looks like a comparison if ( a=true)...
• System.exit() in try-catch-finally blocks.
• Uninitialized variable references with no path of proper initialization.
• Order of try-catch-finally blocks matters.
• main() can be declared final.
• -0.0 == 0.0 is true.
• A class without abstract methods can still be declared abstract.
• Map doesn’t implement Collection.
• Dictionary is a class, not an interface.
• Collection is an Interface where as Collections is a helper class.
• Class declarations can come in any order ( derived first, base next etc. ).
• Forward references to variables gives compiler error.
• Multi dimensional arrays can be sparce ie., if you imagine the array as a matrix, every row need not
have the same number of columns.
• Arrays, whether local or class-level, are always initialized,
• Strings are initialized to null, not empty string.
• An empty string is NOT the same as a null string.
• A declaration cannot be labelled.
• continue must be in a loop ( for, do , while ). It cannot appear in case constructs.
• Primitive array types can never be assigned to each other, eventhough the primitives themselves can be
assigned. ie., ArrayofLongPrimitives = ArrayofIntegerPrimitives gives compiler error eventhough
longvar = intvar is perfectly valid.
• A constructor can throw any exception.
• Initilializer blocks are executed in the order of declaration.
• Instance initializer(s) gets executed ONLY IF the objects are constructed.
• All comparisons involving NaN and a non-Nan would always result false.
• Default type of a numeric literal with a decimal point is double.
• integer (and long ) operations / and % can throw ArithmeticException while float / and % will never,
even in case of division by zero.
• == gives compiler error if the operands are cast-incompatible.
• You can never cast objects of sibling classes( sharing the same parent ), even with an explicit cast.
• .equals returns false if the object types are different. It does not raise a compiler error.
• No inner class can have a static member.