Have created an API for a production environment
Use source control exclusively, Git preferably
Use ftp to deploy applications
…critical. If your API will be consumed by iOS devices, choosing binary property lists over XML or JSON can give you a 30% performance boost as well as an associated reduction in bandwidth consumption. Building an API that generates plists is straightforward with the help of a couple of Ruby gems.
I'll be sharing code examples from a recent project that surfaced a large, multi-faceted API to hundreds of iOS devices using binary plists. I'll also have plenty of resources …
XML Parameter parsing has been sent to a plugin
Working with threaded servers out of the box
Ruby's not the only language that goes well withthat got an update. Check out 1.5!
Here are the major changes in CoffeeScript :
First release of Literate CoffeeScript .
The CoffeeScript REPL is now based on the Node.js REPL, and should work better and more familiarly.
Returning explicit values from constructors is now forbidden. …
Weeks of February 11 - February 25, 2013
9d9b22f4 is another tweak to loading, reversing some earlier decisions. paths and eager load paths will be separate for 4.0 after all.
c9909db9 drops XML parsing from . If you need it, you can pick upt he new actionpack-xml_parser gem.
d3688e02 removes the auto-explain option for . You can still call explicitly ActiveRecord::Relation#explain. I'll miss this, but I know …
Entity expansion vulnerability in ( XML bomb)
And some small bugfixes are also included.
You can download this release from:
<URL:ftp://ftp.ruby-lang.org/pub/ ruby/1.9/ruby-1.9.3-p392.tar.bz2> SIZE: 10024221 bytes MD5: a810d64e2255179d2f334eb61fb8519c SHA256: 5a7334dfdf62966879bf539b8a9f0b889df6f3b3824fb52a9303c3c3d3a58391
<URL:ftp://ftp.ruby-lang.org/pub/ ruby/1.9/ruby-1.9.3-p392.tar.gz> …
When reading text nodes from an XML document, the REXML parser can be coerced in to allocating extremely large string objects which can consume all of the memory on a machine, causing a denial of service.
Impacted code will look something like this: document = REXML::Document.new some_xml_doc document.root.text
When the `text` method is called, entities will be expanded. An attacker can send a relatively small XML document that, when the entities are resolved, will consume extreme amounts …
…in your feed reader or email inbox (depending on your subscription preferences). Because of the new XML feed generated by, it's also likely that many feed readers will show sixteen or so unread posts. I apologize in advance for the noise; unfortunately, this is the inevitable cost of the changeover. This post is the only one that's actually new, so you can just mark all the other posts as read.
Now back to our regularly scheduled program .
AWS OpsWorks - Flexible - in the Cloud Using Chef management tool from .
Instrumental - app monitoring with pretty dashboards.
sublimetext_indentxml - Useful ST2 plugin if you're forced to deal with XML.
Capybara, synchronize, and monkeys that climb ivory towers - Making Capybara wait for .
So commit ).can manipulate XML as a language-level thing. This is both terrifying and, in the case of emitting inline within a Scalatra action, useful. But the limit of this is that not-quite-valid XML, but perfectly reasonable HTML, will cause your Scala program to flat-out not compile. Ergo, I decided it was time to bite the bullet and move my HTML bits into an actual template (
That turned out to be pretty easy. Read the Scalate ( Scalatra view templates) …
First off the schema tables. CREATE TABLE `archive_table` ( `id` int(11) NOT NULL AUTO_INCREMENT, `dat` varchar(1000) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=ARCHIVE DEFAULT CHARSET=latin1; CREATE TABLE `compressed_data` ( `id` int(11) NOT NULL AUTO_INCREMENT, `dat` blob, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT …