Scribd
Upload
3 views

data mining

The document discusses various aspects of CORBA, including client and server applications, interoperability, and challenges such as complexity and overhead. It also covers communication protocols like HTTP and SOAP, time synchronization in distributed systems, and the process of initiating and recording global states through snapshots. Additionally, it evaluates the consistency of global states recorded during the snapshot process.

Uploaded by

shriyuktasinha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

data mining

The document discusses various aspects of CORBA, including client and server applications, interoperability, and challenges such as complexity and overhead. It also covers communication protocols like HTTP and SOAP, time synchronization in distributed systems, and the process of initiating and recording global states through snapshots. Additionally, it evaluates the consistency of global states recorded during the snapshot process.

Uploaded by

shriyuktasinha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

Should Discuss about


• Client Applications
• Server Applications
• ORB
• IDL
• Naming Service
• Fault Tolerance and High Availability
Benefits of using CORBA
• Language and Platform Independence:
• Interoperability
• Scalability
• Flexibility
challenges associated with using CORBA
• Complexity: (Middleware)
• Overhead: (Marshalling and Unmarshalling)
Above all should be discussed with respect to given context
2. • Use HTTP as the underlying protocol for communication.
• Implement SOAP (Simple Object Access Protocol) for message exchange.
• Utilize XML (eXtensible Markup Language) for structuring data within SOAP
messages.

Communication Protocols and Message Formats


SOAP Messages and XML Schemas
Security Measures
Error Handling Strategies
Scalability Techniques
3. Designate a Time Server: Choose one of the nodes in the distributed system to act as the
time server. This node will be responsible for providing the current time to other nodes.

Client Requests: Client nodes periodically request the time from the time server.

Time Response: Upon receiving a request, the time server responds with its current time.

Calculating Offset: Each client node calculates the offset between its local clock and the
time received from the time server. This offset represents the network latency between
the client and the time server.

Adjusting Local Clock: Client nodes adjust their local clocks based on the calculated
offset. The adjustment can be done by adding or subtracting the offset from the local
time.

Should also discuss about how the system handles for Network Latency Fluctuations,
Time Server Downtime.
4. Initiating the Snapshot: Any process in the distributed system can initiate the snapshot
recording process. This is done by sending a special message called a marker along all
outgoing channels.

Recording Local State: Upon receiving a marker on an incoming channel, a process


records its local state, which includes the contents of its memory and any messages
queued to be sent. The process also records the state of the channel on which it received
the marker as empty.

Forwarding Markers: After recording its local state, the process sends a marker along
each of its outgoing channels on which it has not already sent one. This ensures that all
processes eventually receive a marker.

Termination: The snapshot recording process terminates when each process has received
markers on all of its incoming channels.

Collecting Global State: Once the snapshot recording process has terminated, each
process sends its local state to a designated coordinator process. The coordinator
process then assembles the global state from the individual local states and makes it
available to all processes in the system.

At station A
GS1 at Site 1: Global state recorded at station A for the first time

Station A status – S1 = 480, C12 – 120


Marker Message initiated to station B
After Marker message reception at Station B
Station B status – S2=200, C21- 0
Total=800
So, GS1 is consistent global state recording

Station B initiating a Global recording GS2

Station B status – S2 = 120, C12 – 80


Marker Message initiated to station A
After Marker message reception at Station A
Station B status – S1=480, C12- 120
Total=800
So, GS2 is also consistent global state recording

5. GS1 is Inconsistent, because in message transmission from e12 to e22, receiving event is
covered but not the sending event

GS2 - consistent, No future events are covered without covering its past events

Gs3 – Also Consistent, No future events are covered without covering its past events

You might also like