I will discuss the advantages and disadvantages of each approach and show you what to consider when choosing between the two.
An identical copy of you lives your life again. Not in the same way it has an account number.
I often see setters used where information relating to an object is not known at construction time, and needs to be added later.
Packet exchange occurs, with every packet sent being ACKed.
Its all about the SYNs, FINs and ACKs.
Oh, and the PSHes and RSTs. Scale by spawning threads?
When its time to end the conversation, the first party to hang up sends a FIN, then waits for an ACK and a corresponding FIN from the other party.
Even more useful would be to make the default classloader understand EAR files as complete units of deployment, and allow different versions of the same jars to exist within different ear files.
There is no tiny portion of the internet that becomes your personal hotline to the other machine.
Both are excellent high-end database servers which can facilitate some of the most complex, large scale applications in the world. One by one they forget who you are and leave.
A man wearing a refuse disposal engineer's uniform appears from nowhere and assassinates you, placing your body into a recycling bin.
The database is the backbone of your application, the root, the foundation, and the place of storage for all meaningful data contained in your software.
Later, you both attempt to spend the same money twice.
You reach into the engine and take out the starter motor. She also uses a rough logo and artwork that must merged, and shows how to convert those two images into one in ten easy steps, including how to layout that artwork for the transfer sheet.
Getting this kind of relationship right is at the heart of OO design. Most of the time solving them involves hooking up the debugger and stepping through going, 'its fine here. There is only so much cpu to go around.
Should anyone attempt to interact with you before your organs have finished arriving you will die. The database is the backbone of your application, the root, the foundation, and the place of storage for all meaningful data contained in your software.
The present jar based paradigm simply does not allow me that encapsulation.