Mr.Ram.A.Dayinaboyina today..................

 

NETWORK PORTS AND THEIR FUNCTIONS.................................Port 1521 is the default port for the Oracle TNS (Transparent Network Substrate) listener, which is used for communication between an Oracle database server and client applications. It facilitates client connections to the database server using the SQL*Net protocol

 

Title : Ennenno janmala Movie: Pooja Singers: S.P. Bala Subramanyam గారు , Vani Jayaram గారు Lyricist: Composer: Raajan Nagendran గారు Director: Murugan Kumaran గారు

 ఎన్నెన్నో జన్మల బంధం నీది నాది... ఎన్నటికి మాయని మమతా నాది నీది

ఒక్క క్షణం నిను వీడి నేనుండలేను.. ఒక్క క్షణం నీ విరహం నేతాళలేను
ఎన్నెన్నో జన్మల బంధం నీది నాది... ఎన్నటికి మాయని మమతా నాది నీది

పున్నమి వెన్నెలలోన పొంగును కడలి... నిన్నే చూసినవేళ నిండును చెలిమి
నువ్వు కడలివైతే నే నదిగ మారి చిందులు వేసి వేసి నిన్ను చేరనా చెరనా..చెరనా...
ఎన్నెన్నో జన్మల బంధం నీది నాది... ఎన్నటికి మాయని మమతా నాది నీది

విరిసిన కుసుమము నీవై మురిపించేవు.. తావి నేనై నిన్ను పెనవేసేను
మేఘం నీవై  నెమలిని నేనై ఆశతొ నిన్ను చూసి చూసి ఆడనా.. ఆడనా.. ఆడనా..
ఎన్నెన్నో జన్మల బంధం నీది నాది... ఎన్నటికి మాయని మమతా నాది నీది

కోటి జన్మలకైన కోరేదొకటే.. నీలొ సగమై ఎపుడు నేనుండాలి
నీవున్నవేళ ఆ స్వర్గమేలా ఈ పొందు ఎల్లవేళలందు ఉండనీ.. ఉండనీ.. ఉండనీ..
ఎన్నెన్నో ఎన్నెన్నో జన్మల బంధం నీది నాది...
ఎన్నటికి ఎన్నటికి మాయని మమతా నాది నీది
ఒక్క క్షణం నిను వీడి నేనుండలేను

from my FB.................Mr Ramu..........

 

Mr Ram.A.Dayinaboyina.................

 

Mr.Ram.A.Dayinaboyina........................

 

Mr.Ram.A.Dayinaboyina...............................Blr T1......

 

Mr.Ram.A.Dayinaboyina..........................

 

Aarna Dayinaboyina .................

 

A Memorandum of Understanding (MOU)..............

 .................. outlines the terms of an agreement between two or more parties, often before a formal contract is established. Key elements include the parties involved, the project or purpose of the MOU, each party's responsibilities, the scope of work, timelines, and termination clauses. MOUs are generally not legally binding, but they do serve as a record of the parties' intentions and can be a crucial first step towards a more formal agreement. 

Here's a more detailed breakdown of common MOU contents:

1. Parties Involved: 

• The names and contact information of all parties entering into the agreement.

2. Purpose and Objectives: 

• A clear statement of the reason for the MOU and the goals that the parties hope to achieve.

3. Scope of Work: 

• A detailed description of the specific activities, tasks, or project that the MOU covers.

4. Roles and Responsibilities: 

• Clearly defined tasks and obligations for each party involved.

5. Timelines and Milestones: 

• Specific dates or periods for the completion of tasks or the achievement of objectives.

6. Financial Arrangements: 

• If applicable, details about any financial contributions, payments, or cost-sharing arrangements.

7. Confidentiality: 

• A clause outlining how confidential information shared between parties will be protected.

8. Dispute Resolution: 

• A process for resolving disagreements or conflicts that may arise.

9. Termination Clause: 

• Conditions under which the MOU can be terminated by either party.

10. Governing Law: 

• The jurisdiction whose laws will govern the interpretation and enforcement of the MOU.

11. Signatures: 

• Spaces for authorized representatives of each party to sign and date the MOU.

12. Amendments: 

• A clause outlining the process for making changes to the MOU.

13. Intellectual Property: 

• A clause regarding the protection of intellectual property rights generated from the cooperation.

While MOUs are generally not legally binding, they can be legally binding if they contain specific language indicating such an intention and fulfill the requirements of a contract under applicable law

Mr.Dayinaboyina.................................

An RMI (Remote Method Invocation) exception, specifically java.rmi.RemoteException, is a general exception thrown when a remote method call fails during execution. This can occur due to various reasons, including network connectivity issues, the server not being available, or errors during the remote method invocation process.

Elaboration:

• RemoteException:

  This is the base class for most RMI-related exceptions. It's designed to handle communication errors during remote method calls. 
• Causes of RemoteException:

  • Network Issues: Problems with the network connection between the client and server can lead to RemoteException. 
  • Server Unavailable: If the server is not running or is not accessible, a RemoteException will be thrown. 
  • Errors During Method Invocation: If the server encounters an error while processing the remote method call (e.g., an exception during the method's execution, or an error unmarshalling arguments), it can also result in a RemoteException. 
• RemoteException is a wrapper:

  In some cases, RemoteException might wrap another exception that occurred during the remote call. This allows the client to understand the root cause of the failure, even if it's a more specific exception thrown by the server. 
• Handling RemoteException:

  • Remote interfaces in Java must declare RemoteException in their throws clause. 
  • Clients should handle RemoteException to gracefully deal with failures in remote method calls. 
• Examples of RMI Exceptions:

  • ConnectException: Thrown when a connection to the remote host is refused. 
  • ServerException: Thrown when an exception occurs on the server while processing a remote method invocation. 
  • SkeletonNotFoundException: Thrown when the skeleton class for a remote object cannot be found. 
  • NamingException: Thrown during RMI naming operations (e.g., binding and unbinding).