Part II Third-party frameworks and Libraries the first part of this book takes a deep dive into II main LIBRARIES:DR B and Rinda
- Chapter3:ringydingy
-
- including 6 parts:
-
- Installation
- Getting Started with Ringydingy
- "Hello World" the Ringdingy
- Building a distributed Logger with Ringydingy
- Letting Ringydingy Shine
- Conclusion
- Installation
-
- Command:gem Install Ringydingy
- Show: successfully installed RingyDingy-1.6
- Getting Started with Ringydingy
-
- A quick look at the what options is available on ring_server
- Start our ringydingy ringserver with command
- Ring_server--v
- We get:
- "Hello World" the Ringydingy
-
- Our server code for the rinda ' Hello world ' application remains largely unchanged to use with Ringydingy
- Server
- We'll see output similar to the following for our ringydingy Ringserver:
- Client
- Output
- Binding a distributed Logger with Ringydingy
-
- Ringydingy allows us to DRY up our server code a bit. We no longer have the remember a whole lot of messy rinda API calls. Instead, we can wrap it up with a line or both of ringydingy code. Let's look at our "distributed Logger" application to see how we can make it more DRY.
- Server
- Client
- Ring_server output
- Server output
- Client output
- Letting Ringydingy Shine
-
- One of the better features that the ringydingy ring_server binary gives your for free are the ability to list available Serv Ices.
- We can also gain access to this same information programmatically. An Example:page85
- Conclusion
"Distributed programming with Ruby" Reading notes five ringydingy (Part2 Chapter3)
