Friday, July 29, 2011

Ladder theory - stairway to heaven?

Basics of the ladder theory

The basic premise of Ladder Theory is that all men gauge women on an I-would-have-sex-with-this woman/how-likely-is-she-to-have-sex-with-me scale.
Women apparently have two ladders:
  • Potential sexual partners, and
  • Platonic partners - those she would never have sex with.
Given that women are arguably a lot more more complex than men, then that figures..
Classification and ranking (for both sexes) is described as a 'Ladder' hence the name Ladder Theory.
Allegedly, the higher up on someone's ladder you are the more likely you are to get laid.
The following (basic) table sets out how men and women apparently make their initial mental assessment of each other.

ladder theory male/female assessment factors

How attractive is she60How much money/power does he have50
How soon she will have sex with me30How attractive is he*40
Other aspects10How much women say and don't mean (e.g., I prefer a man with a sense of humour, a sensitive man, etc)10
* Attractive (40%) to women is broken down as follows:
  • 50% - Physical Attraction
  • 20% - Competition (is he someone else's, does he ignore me, I-want-what-I-can't-have, etc..)
  • 20% - Novelty (women it appears lay some kudos on men being 'novel')
  • 10% - Other (we can only guess..)

men's ladders

Based on the above, a man will place a woman highest on his ladder if (he judges) she is willing to have sex with him and he finds her attractive.
It could be said that most men and women would not find that statement ground-breaking.
Men apparently classify women as follows:
  1. Top - (of course) is the woman he really/most fancies.
  2. Next - the women who he would have sex with and admit to.
  3. Last - those women he would have sex with but never admit to it (or be too drunk to remember who she was). Too much alcohol can as we know make even the most unattractive woman (and man) appear desirable.
As an aside it should be remembered that beauty is subjective, and (often) superficial, especially when applied to women (although some men also prefer not to be to seen without their make-up or other physical enhancements).
Men, as stated in the Ladder Theory, do not have a ladder for 'Platonic' females since the theory works on the premise that all men basically evaluate women as sexual objects.

women's ladders

Women as stated earlier have two ladders - Potential Sexual Partners and Platonic Partners.
The first problem here for men is that they often don't know which ladder they are on.
When they do get it wrong they can come to an 'abysmal' end.
Women place Money/Power as a man's most attractive aspect.
This is borne out by how many 'not very attractive' powerful rich men have beautiful women companions. (If the cap fits..)


Do not stand at my grave and weep,
I am not there, I do not sleep.
I am a thousand winds that blow.
I am the diamond glint on snow.
I am the sunlight on ripened grain.
I am the gentle autumn rain.
When you wake in the morning hush,
I am the swift, uplifting rush
Of quiet birds in circling flight.
I am the soft starlight at night.
Do not stand at my grave and weep.
I am not there,  I do not sleep.
Do not stand at my grave and cry.
I am not there,  I did not die!
Do not stand at my grave and weep.
I am not there,  I do not sleep.
I am the song that will never end.
I am the love of family and friend.
I am the child who has come to rest
In the arms of the Father
who knows him best.
When you see the sunset fair,
I am the scented evening air.
I am the joy of a task well done.
I am the glow of the setting sun.
Do not stand at my grave and weep.
I am not there, I do not sleep.
Do not stand at my grave and cry.
I am not there, I did not die!

Wednesday, April 20, 2011

Awesome piece of poetry

Here i am sitting in my home @ night…
Thinking hard about life
How it changed from a maverick collage life to strict professional life…...

How tiny pocket money changed to huge monthly paychecks
but then why it gives less happiness….

How a few local denim jeans changed to new branded wardrobe
but then why there are less people to use them

How a single plate of samosa changed to a full Pizza or burger
But then why there is less hunger…..

Here i am sitting in my home @ night…
Thinking hard about life
How it changed…..

How a bike always in reserve changed to bike always on
but then why there are less places to go on……

How a small coffee shop changed to cafe coffee day
but then why its feels like shop is far away…..

How a limited prepaid card changed to postpaid package
but then why there are less calls & more messages……

Here i am sitting in my home @ night…
Thinking hard about life
How it changed…..

How a general class journey changed to Flight journey
But then why there are less vacations for enjoyment….

How a old assembled desktop changed to new branded laptop
but then why there is less time to put it on……….

How a small bunch of friends changed to office mate
but then why after 8 o' Clock it always feel like getting late….

Here i am sitting in my home @ night…
Thinking hard about life
How it changed….. how it changed……..

Friday, February 18, 2011

JAVA1.6 enhancement

Java 1.6 was released to overcome a few shortcomings and provide enhanced features when compared to Java 1.5

Details of 1.6 are mentioned below.

Advantages to running applications on Java SE 6
Applications run faster on the desktop and servers
New 'Dynamic Attach' diagnostics simplify troubleshooting
Expanded Solaris DTrace support provides additional value on Solaris
Improved 'native' look and feel across Solaris, Linux, and Windows
First Java platform with full support for Windows Vista
Benefits in upgrading developer environments to Sun's Java SE 6
JavaScript integrated and included with the platform
Scripting languages framework extends support for Ruby, Python, and other languages
Complete light-weight platform for web services, right out of the box
Simplified GUI design and expanded native platform support
Full JDBC4 implementation providing improved XML support for Databases
Java DB included with the JDK, a free to use and deploy Java Database
Full support by NetBeans IDE 5.5
Sun Developer Services available to help build more robust applications
Improved User Experience

Look-and-feel updates to better match underlying operating system
Improved desktop performance and integration
Enhanced internationalization support
Improved performance
Upwards binary compatibility

Security Features and Enhancements

Native platform Security (GSS/Kerberos) integration.
Java Authentication and Authorization Service (JAAS) login module that employs LDAP authentication
New Smart Card I/O API
Native security services technical article
» Find out more

Integrated Web Services

New API for XML digital signature services for secure web services
New Client and Core Java Architecture for XML-Web Services (JAX-WS) 2.0 APIs
New support for Java Architecture for XML Binding (JAXB) 2.0
XML home page
» Find out more

Scripting Language Support (JSR 223)

New framework and API for scripting languages
Mozilla Rhino engine for JavaScript built into the platform
Scripting for the Java Platform technical article
» Find out more

Enhanced Management and Serviceability

Improved JMX Monitoring API
Runtime Support for dTrace (Solaris 10 and future Solaris OS releases only)
Improved memory usage analysis and leak detection
Monitoring and Management technical article

Increased Developer Productivity

JDBC 4.0 support (JSR 221)
Significant library improvements
Improvements to the Java Platform Debug Architecture (JPDA) & JVM Tool Interface

Collections Framework Enhancements

This page summarizes enhancements to the collections framework in Java SE 6.
This release saw fewer API changes than 5.0, but there was more of a focus on the accuracy and clarity of the specification. We recommend using the Java SE 6 specification even when writing programs for older releases.
The primary theme of the API changes was better bi-directional collection access.
These new collection interfaces are provided:
• Deque - a double ended queue, supporting element insertion and removal at both ends. Extends the Queue interface.
• BlockingDeque - a Deque with operations that wait for the deque to become non-empty when retrieving an element, and wait for space to become available in the deque when storing an element. Extends both the Deque andBlockingQueue interfaces. (This interface is part of java.util.concurrent.)
• NavigableSet - a SortedSet extended with navigation methods reporting closest matches for given search targets. A NavigableSet may be accessed and traversed in either ascending or descending order. This interface is intended to supersede the SortedSet interface.
• NavigableMap - a SortedMap extended with navigation methods returning the closest matches for given search targets. A NavigableMap may be accessed and traversed in either ascending or descending key order. This interface is intended to supersede the SortedMap interface.
• ConcurrentNavigableMap - a ConcurrentMap that is also a NavigableMap. (This interface is part of java.util.concurrent.)
The following concrete implementation classes have been added:
• ArrayDeque - efficient resizable-array implementation of the Deque interface.
• ConcurrentSkipListSet - concurrent scalable skip list implementation of the NavigableSet interface.
• ConcurrentSkipListMap - concurrent scalable skip list implementation of the ConcurrentNavigableMap interface.
• LinkedBlockingDeque - concurrent scalable optionally bounded FIFO blocking deque backed by linked nodes.
• AbstractMap.SimpleEntry - simple mutable implementation of Map.Entry
• AbstractMap.SimpleImmutableEntry - simple immutable implementation of Map.Entry
These existing classes have been retrofitted to implement new interfaces:
• LinkedList - retrofitted to implement the Deque interface.
• TreeSet - retrofitted to implement the NavigableSet interface.
• TreeMap - retrofitted to implement the NavigableMap interface.
Two new methods were added to the Collections utility class:
• newSetFromMap(Map) - creates a general purpose Set implementation from a general purpose Map implementation.
There is no IdentityHashSet class, but instead, just use
Set identityHashSet=
new IdentityHashMap());
• asLifoQueue(Deque) - returns a view of a Deque as a Last-in-first-out (Lifo) Queue.
The Arrays utility class now has methods copyOf and copyOfRange that can efficiently resize, truncate, or copy subarrays for arrays of all types.
int[] newArray = new int[newLength];
System.arraycopy(oldArray, 0, newArray, 0, oldArray.length);
int[] newArray = Arrays.copyOf(a, newLength);

JavaTM RMI Release Notes
for JDKTM 6

Enhancements in JavaTM SE Development Kit (JDK) 6
java.rmi.MarshalledObject now generic
The class MarshalledObject now has a type parameter representing the type of the contained serialized object.
Bug fix: Explicit TCP ports freed after remote objects unexported (4457683)
In previous releases, after a remote object had been exported on an explicit (non-anonymous) TCP port, the RMI implementation would keep a server socket bound to that port open for the lifetime of the virtual machine, regardless of the life cycle of remote objects exported on that port. This bug has been fixed so that after all remote objects that had been exported on a given non-anonymous port have become unexported (either explicitly or through distributed garbage collection) then the associated server socket will be closed. (There is an equivalent bug for anonymous TCP ports: 6279965.)
Bug fix: Garbage collection of client socket factories (4486732)
In previous releases, after a remote invocation was made on a remote stub containing a non-null RMIClientSocketFactory in a given virtual machine, then either that factory object or an equivalent factory object would remain forever reachable in the virtual machine, preventing it (and its defining class loader) from ever being garbage collected; this bug has been fixed. (There is an equivalent bug for socket factories used to export a remote object: 6332603.)
Default GC interval lengthed to one hour (6200091)
In previous releases, the maximum interval between garbage collections of the local heap enforced by the RMI implementation (while there are live remote references or exported remote objects), which is controlled by the system properties sun.rmi.dgc.client.gcInterval and sun.rmi.dgc.server.gcInterval, was one minute by default. The default interval is now one hour, to better accommodate applications with large heap sizes without special configuration.
Enhancements and Changes in Previous Releases
Dynamic Generation of Stub Classes (since 5.0)
This release adds support for the dynamic generation of stub classes at runtime, obviating the need to use the Java Remote Method Invocation (Java RMI) stub compiler, rmic, to pregenerate stub classes for remote objects. Note that rmic must still be used to pregenerate stub classes for remote objects that need to support clients running on earlier versions.
When an application exports a remote object (using the constructors or static exportObject methods1 of the classes java.rmi.server.UnicastRemoteObject orjava.rmi.activation.Activatable) and a pregenerated stub class for the remote object's class cannot be loaded, the remote object's stub will be a java.lang.reflect.Proxy instance (whose class is dynamically generated) with a java.rmi.server.RemoteObjectInvocationHandler as its invocation handler.
An existing application can be deployed to use dynamically generated stub classes unconditionally (that is, whether or not pregenerated stub classes exist) by setting the system propertyjava.rmi.server.ignoreStubClasses to "true". If this property is set to "true", pregenerated stub classes are never used.
• If a remote object has pre-5.0 clients, that remote object should use a stub class pregenerated with rmic or the client will get an ClassNotFoundException deserializing the remote object's stub. Pre-5.0 clients will not be able to load an instance of a dynamically generated stub class, because such a class contains an instance of RemoteObjectInvocationHandler, which was not available prior to this release.
• Prior to the J2SE 5.0 release, exporting a remote object would throw a java.rmi.StubNotFoundException if the pregenerated stub class for the remote object's class could not be loaded. With the added support for dynamically generated stub classes, exporting a remote object that has no pregenerated stub class will silently succeed instead. A user deploying a server application to support pre-5.0 clients must still make sure to pregenerate stub classes for the server's remote object classes, even though missing stub classes are no longer reported at export time. Such errors will instead be reported to a pre-5.0 client when it deserializes a dynamically generated stub class.
1 The static method UnicastRemoteObject.exportObject(Remote) is declared to return java.rmi.server.RemoteStub and therefore cannot be used to export a remote object to use a dynamically generated stub class for its stub. An instance of a dynamically generated stub class is a java.lang.reflect.Proxy instance which is not assignable to RemoteStub.
Standard SSL/TLS Socket Factory Classes (since 5.0)
This release adds standard Java RMI socket factory classes, javax.rmi.ssl.SslRMIClientSocketFactory and javax.rmi.ssl.SslRMIServerSocketFactory, which communicate over the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols using the Java Secure Socket Extension (JSSE). These socket factory classes provide a simple way to use JSSE with Java RMI, enabling enforcement of integrity, confidentiality (through encryption), server authentication, and (optionally) client authentication for remote method invocations. For more information on how to use custom socket factories with Java RMI, see the tutorial "Using Custom Socket Factories with Java RMI". For more information on JSSE (including how to configure it), see the JSSE Reference Guide.
Launching rmid or a Java RMI Server from inetd/xinetd (since 5.0)
A new feature, provided by the System.inheritedChannel method, allows an application to obtain a channel (java.nio.channels.SocketChannel or java.nio.channels.ServerSocketChannel, for example) inherited from a process that launched the virtual machine (VM). Such an inherited channel can be used to either service a single incoming connection (in the case of a SocketChannel) or accept multiple incoming connections (in the case of ServerSocketChannel). Therefore, Java networking applications launched by inetd (Solaris(tm) Operating System) or xinetd (Linux) can now obtain theSocketChannel or ServerSocketChannel inherited from inetd/xinetd.
With the addition of this feature, the Java RMI activation daemon rmid has been enhanced to support being launched from inetd/xinetd so that rmid can be started up only when it receives an incoming connection. For details on the enhancements to rmid to support this feature, see the tools page for rmid (for the Solaris Operating System). For details on how to configure inetd to launch rmid, see the tutorial "Configuring inetd to Launch rmid".
An application using Java RMI can also be designed to be launched from inetd or xinetd. For an example on how to implement this technique, see the tutorial "Designing Services to be Launched frominetd."
rmic default stub protocol version option now -v1.2 (since 5.0)
When rmic is run without an option to specify the JRMP stub protocol version to be used by the generated classes, it now behaves as if the -v1.2 option were specified, instead of the -vcompat option as in previous releases.
This change means that by default, rmic does not generate any skeleton classes and generates stub classes that only implement the 1.2 stub protocol version. If a remote implementation class needs to be built to support clients running on JDK 1.1, then the -vcompat option must now be specified explicitly. (Also, note that as described above, if a remote implementation class does not need to support clients running on any release prior to 5.0, then rmic does not need to be run at all for that class.)
See the tools documentation for rmic [Solaris and Linux] [Windows] for more information about these command line options.
rmic no longer compiles arbitrary source files in the class path (since 5.0)
In previous releases, rmic would sometimes, while processing its input class files, attempt to compile arbitrary .java source files that it encountered in the class path. In 5.0, rmic does not attempt to compile any source files other than those for the stub, skeleton, or tie classes that it generates.
The expectation is that the remote implementation classes passed to rmic, as well as all classes and interfaces that they depend on, have already been successfully compiled with javac before rmic is run. If an existing build procedure depends on the previous behavior of rmic for compiling some of its application source files, then that build procedure will need to be modified to ensure that all necessary classes are correctly compiled with javac before running rmic.
Server-side Stack Traces Now Retained in Remote Exceptions (since 1.4)
The Java RMI runtime implementation will now preserve the server-side stack trace information of an exception that is thrown from a remote call, in addition to filling in the client-side stack trace as it did in previous releases. Therefore, when such an exception becomes accessible to client code, its stack trace will now contain all of its original server-side trace data followed by the client-side trace.
This feature is made possible by the new "programmatic access to stack trace information" feature of java.lang.Throwable in J2SE 1.4, which included making a Throwable's stack trace data part of its default serialized form. What the client-side Java RMI runtime implementation now does to cooperate with this feature is to append the client-side trace to the unmarshalled server-side trace, rather than simply overwriting with the client-side trace as it did in previous releases.
Certain server applications may wish to prevent any server-side stack trace data from accompanying an exception to be marshalled as the result of a remote call (as part of the exception's default serialized form in J2SE 1.4), perhaps for reasons of performance or confidentiality. In such cases, the implementation-specific system property
can be set to "true" to cause the server-side Java RMI runtime implementation to clear the stack traces of all exceptions thrown from the current virtual machine as the result of remote method invocations.
Service Provider Interface for RMIClassLoader (since 1.4)
Certain static methods of java.rmi.server.RMIClassLoader now delegate their behavior to an instance of a new service provider interface, java.rmi.server.RMIClassLoaderSpi. The service provider can be configured to augment the Java RMI dynamic class loading behavior for a given application. By default, the service provider implements the standard behavior of all of the static methods inRMIClassLoader. See the class documentation of RMIClassLoader and RMIClassLoaderSpi for more details.
Dynamic Server Host Name (since 1.4)
The java.rmi.server.hostname property can now be dynamically updated to indicate that future exports should use a new host name. Therefore, the new host name value will be contained in the stub for an object that is exported after the property is updated.
HTTP Fallback Is More Configurable (since 1.4.1)
The implementation-specific system property sun.rmi.transport.proxy.eagerHttpFallback has been added to allow additional control over when the Java RMI default socket factory will fall back to HTTP tunneling. This property configures the default socket factory so that any SocketException thrown by an initial (direct) connection attempt will trigger HTTP tunneling; this more "eager" fallback strategy can be useful when dealing with firewalls which deny instead of ignore connection attempts to unauthorized ports.
java.rmi.Naming.list Method No Longer Prepends a Scheme to Names Returned (since 1.4.1)
In previous releases, the Naming.list method prepended the scheme rmi: to each name contained in the returned array of strings. The Naming.list implementation now matches the specification, returning an array of names that are URL-formatted, but without the scheme component.
java.rmi.activation.ActivationGroupDesc (since 1.3)
The getClassName method, which returns the group's class name, can now return null, indicating the system's default group implementation. Previously, the getClassName method would return the name of the internal implementation class if the default group implementation was chosen when the descriptor was constructed.
Due to this change, if an application running in a 1.3 virtual machine registers an new activatable object with the ActivationSystem, rmid must also be upgraded to run 1.3, since a pre-1.3 rmid will not be able to activate the newly registered activatable object.
The Java RMI Stub Compiler, rmic (since 1.3)
By default, rmic [Solaris and Linux] [Windows] now assumes that the destination directory for generated stubs is the package-named subdirectory of the current working directory. If the "-d" option is not specified, the result is the same as though it were specified with the current working directory "." as an argument. The "-d" may still be used to override the default destination directory.
Two new options, "-idl" and "-iiop" have been added to generate IDL and stubs for IIOP, respectively.
The Java RMI Activation Daemon, rmid (since 1.3)
By default, rmid [Solaris and Linux] [Windows] now requires a security policy file.
Serializing remote objects (since 1.2.2)
Prior to 1.2.2, an attempt to pass an unexported remote object in a RMI call would result in a java.rmi.StubNotFoundException. This exception was a result of the RMI runtime's failure to locate a stub object during an attempt to replace a remote object implementation with its corresponding stub. In 1.2.2 and later releases, an unexported remote object passed in an RMI call will no longer result in an exception, but rather the remote object will be serialized instead of its stub. If the remote object implementation is not serializable, an attempt to pass an unexported object in an RMI call will result in ajava.rmi.RemoteException with the nested exception

Serialization Changes and Enhancements
in JavaTM SE Development Kit 6

The following are enhancements to serialization in Java SE Development Kit 6 (JDK). For a summary of enhancements in previous releases, see Enhancements in Previous Releases.
In previous releases, it was difficult to programmatically obtain an ObjectStreamClass instance for a non-serializable Class, although doing so can be desirable when customizing the stream format for class descriptors (see 4413615 for more information). The new method ObjectStreamClass.lookupAny can now be used for this purpose.
Bug fix: delayed garbage collection
In previous releases, bug 6232010 could cause serializable classes and subclasses of ObjectOutputStream and ObjectInputStream to be strongly referenced long after their use in a serialization operation, thus possibly delaying garbage collection of their defining class loaders indefinitely. Internal caches in the serialization implementation have been restructured to fix this bug.