Archive for April 2010
The father was kind of scared so he asked his little daughter,
'Sweetheart, please hold my hand so that you don't fall into the river.'
The little girl said, 'No, Dad. You hold my hand.'
'What's the difference?' Asked the puzzled father.
'There's a big difference,' replied the little girl.
'If I hold your hand and something happens to me,
chances are that I may let your hand go.
But if you hold my hand, I know for sure that no matter what happens,
you will never let my hand go.'
In any relationship, the essence of trust is not in its bind, but in its bond.
So hold the hand of the person who loves you rather than expecting them to hold yours...
This message is too short......but carries a lot of Feelings.
They would call up credit card holders representing themselves as employees of the credit card company. They would inform these clueless customers about a new scheme about new credit cards with greater purchase limits in exchange of old ones. Then they would also inform customers that the company's representative would soon visit them with the new card, which would be activated as soon as they filled in a form!
This news only reinstates the importance of being a vigilant customer and using credit cards with utmost prudence. Here are a few things one can do:
1. If you lose your credit card, it is necessary to inform your credit card company immediately. This will enable the card issuer to freeze the card with immediate effect and prevent any purchases on the card. The important thing for you is that your liability is limited once you inform the credit card issuer.
2. Destroy your old card completely before you begin using your new card. This is important even if your old card has expired or you are upgrading your card.
3. Keep your card in a safe place and do not allow other people to handle it.
4. Be prudent about signing up for new offers. Double-check the genuineness of the scheme. A simple way to verify genuineness of any scheme is to call up the credit card company and inquiring with them.
5. Change your PIN at regular intervals. Do not use obvious PIN like birth dates.
6. Inform your credit card company immediately if you do not receive your monthly credit statement. It could be a case of identity theft where the fraudster has changed your billing address.
7. Use chip based credit cards. These cards offer better security than credit cards with black magnetic stripes. This is because in a chip based card, all information is stored in the small chip in encrypted format and it also uses a PIN. This makes changing or copying this data extremely difficult.
8. So, the chance of data being misused while swiping the card is very remote. It is the highest level of security that credit card companies can offer at present. Citibank and Kotak Mahindra issue chip based cards to select high range customers. Axis bank's VISA Platinum card is also chip-based. HDFC Bank also has begun issuing these cards.
9. Be careful while shopping online. This is because you are required to give the CVV number for making purchases over the Internet. For this, be sure you shop only from secure websites. Ensure that the website is certified by VeriSign. Look for a yellow lock on the bottom right hand corner of the screen.
10. If you have a large credit limit on your card and use it frequently for several purchases including online and telephone purchases, it is a good idea to get your card insured. You cannot prevent credit card fraud but at least minimize its impact on your financial stability! You can protect yourself from fraudulent charges on your card up to 12 hours before reporting the loss to the credit card issuer.
- It is fast.
- Supports read-only and read/write caching.
- Supports memory-based and disk-based caching.
- Does not support clustering.
- It is a powerful .
- flexible package
- supports read-only and read/write caching.
- Supports memory- based and disk-based caching.
- Provides basic support for clustering via either JavaGroups or JMS.
- is a cluster-based caching.
- supports read-only or nonstrict read/write caching .
- appropriate for applications those have more read operations than write operations.
- is a powerful replicated and transactional cache.
- useful when we need a true transaction-capable caching architecture .
- Useful for data that is read frequently but never updated.
- It is Simple .
- Best performer among the all.
- Used when our data needs to be updated.
- It’s having more overhead than read-only caches.
- When Session.close() or Session.disconnect() is called the transaction should be completed in an environment where JTA is no used.
- It is never used if serializable transaction isolation level is required.
- In a JTA environment, for obtaining the JTA TransactionManager we must specify the property hibernate.transaction.manager_lookup_class.
- To use it in a cluster the cache implementation must support locking.
- Needed if the application needs to update data rarely.
- we must specify hibernate.transaction.manager_lookup_class to use this in a JTA environment .
- The transaction is completed when Session.close() or Session.disconnect() is called In other environments (except JTA) .
- It supports only transactional cache providers such as JBoss TreeCache.
- only used in JTA environment.
Hibernate 3.0, the latest Open Source persistence technology at the heart of J2EE EJB 3.0 is available for download from Hibernet.org.The Hibernate 3.0 core is 68,549 lines of Java code together with 27,948 lines of unit tests, all freely available under the LGPL, and has been in development for well over a year. Hibernate maps the Java classes to the database tables. It also provides the data query and retrieval facilities that significantly reduces the development time. Hibernate is not the best solutions for data centric applications that only uses the stored-procedures to implement the business logic in database. It is most useful with object-oriented domain modes and business logic in the Java-based middle-tier. Hibernate allows transparent persistence that enables the applications to switch any database. Hibernate can be used in Java Swing applications, Java Servlet-based applications, or J2EE applications using EJB session beans.
Features of Hibernate
* Hibernate 3.0 provides three full-featured query facilities: Hibernate Query Language, the newly enhanced Hibernate Criteria Query API, and enhanced support for queries expressed in the native SQL dialect of the database.
* Filters for working with temporal (historical), regional or permissioned data.
* Enhanced Criteria query API: with full support for projection/aggregation and subselects.
* Runtime performance monitoring: via JMX or local Java API, including a second-level cache browser.
* Eclipse support, including a suite of Eclipse plug-ins for working with Hibernate 3.0, including mapping editor, interactive query prototyping, schema reverse engineering tool.
* Hibernate is Free under LGPL: Hibernate can be used to develop/package and distribute the applications for free.
* Hibernate is Scalable: Hibernate is very performant and due to its dual-layer architecture can be used in the clustered environments.
* Less Development Time: Hibernate reduces the development timings as it supports inheritance, polymorphism, composition and the Java Collection framework.
* Automatic Key Generation: Hibernate supports the automatic generation of primary key for your.
* JDK 1.5 Enhancements: The new JDK has been released as a preview earlier this year and we expect a slow migration to the new 1.5 platform throughout 2004. While Hibernate3 still runs perfectly with JDK 1.2, Hibernate3 will make use of some new JDK features. JSR 175 annotations, for example, are a perfect fit for Hibernate metadata and we will embrace them aggressively. We will also support Java generics, which basically boils down to allowing type safe collections.
* EJB3-style persistence operations: EJB3 defines the create() and merge() operations, which are slightly different to Hibernate's saveOrUpdate() and saveOrUpdateCopy() operations. Hibernate3 will support all four operations as methods of the Session interface.
* Hibernate XML binding enables data to be represented as XML and POJOs interchangeably.
* The EJB3 draft specification support for POJO persistence and annotations.