Explore >> Select a destination
|
You are here 
|
tenderlovemaking.com | ||
| | | | |
kevinjmurphy.com
|
|
| | | | | Why is our Rails app returning different HTTP status codes in different versions of Rails? Learn some tips and tricks for navigating a large ruby code base in this post. | |
| | | | |
www.amberbit.com
|
|
| | | | | ||
| | | | |
www.sethvargo.com
|
|
| | | | | Ruby is an excellent programming language for creating and managing custom DSLs, but how can you securely evaluate a DSL while explicitly controlling the methods exposed to the user? Our good friends instance_eval and instance_exec are great, but they expose all methods - public, protected, and private - to the user. Even worse, they expose the ability to accidentally or intentionally alter the behavior of the system! The cleanroom pattern is a safer, more convenient, Ruby-like approach for limiting the information exposed by a DSL while giving users the ability to write awesome code! The cleanroom pattern is a unique way for more safely evaluating Ruby DSLs without adding additional overhead. | |
| | | | |
sookocheff.com
|
|
| | | So you want to use Thrift? You've come here because you want to use Apache Thrift and you don't know where to start. Good. You're in the right spot. Throughout this document we will develop a simple service that communicates using Thrift. This will introduce you to the workflow for generating client and server code using Thrift and how to Thrift works to separate your application's business logic from it's transport methods. | ||
