Author: Peter Karman (Page 33 of 76)

No, it’s not what I suffer from the lack of (as in sleep). It’s Representational State Transfer. It’s been a buzzword for a few years now. I’m just now reading about it, and thought I would include some highlights here for my own reference.

Read all about it.

From the URL above, REST exhibits the following characteristics:

• Client-Server: a pull-based interaction style: consuming components pull representations.
• Stateless: each request from client to server must contain all the information necessary to understand the request, and cannot take advantage of any stored context on the server.
• Cache: to improve network efficiency responses must be capable of being labeled as cacheable or non-cacheable.
• Uniform interface: all resources are accessed with a generic interface (e.g., HTTP GET, POST, PUT, DELETE).
• Named resources – the system is comprised of resources which are named using a URL.
• Interconnected resource representations – the representations of the resources are interconnected using URLs, thereby enabling a client to progress from one state to another.
• Layered components – intermediaries, such as proxy servers, cache servers, gateways, etc, can be inserted between clients and resources to support performance, security, etc.

Trying to make my CatalystX::CRUD project more RESTful.

If I needed to explain REST to my wife, I could refer her to this.

The Wikipedia CRUD article maps the RESTful verbs to CRUD and SQL actions like so:

However, important to note that REST != CRUD.

update to original post: Another good REST article.

And REST for my kids.

Long before I was a computer programmer I was an essay writer, a songwriter, a poet. When I discovered Perl, I found the transition to programming very natural. I had always played with computers, back to the IBM PC and Macintosh circa 1984. My first program was in BASIC, in 1985. It was a ‘choose your own adventure’-type program. Even then, I wanted to combine prose with code. It was just Making Stuff with Words. I didn’t differentiate.

chromatic suggests Perl programmers can improve their code by thinking in terms of sentences and paragraphs. Best practices. Makes perfect sense to me. When my friends ask me about my work I tell them I’m a writer, that a good piece of Perl code has the same structure and thought behind it as a well-written essay, and that I practice the art of writing every day. It’s just that the language I write in is Perl, not English. I know my metaphor is lost on most non-programmers. But I trust some people understand.

I have a couple different Google Alerts sent to my inbox. Occasionally they turn up something interesting. Today I got a link to an article that mentioned a book on Perl and text mining. Since I work in a technical library building, I checked the online card catalog, walked downstairs and checked it out. It’s now sitting on my desk. Whether I’ll make time to read it remains to be seen.

I’m starting in (again) on KS and Xapian backends for SWISH::Prog, using libswish3.

I just downloaded the latest Xapian release (1.0.10) and latest KS from svn. I started the build process for Xapian first, then svn up’d KS and started the KS build. The KS build finished, and all tests passed, before Xapian even finished its build. That could be due to the speed of the gcc vs g++ compilers. Dunno. It was just a startling thing to notice.

Now back to writing code…