Tag Archives: restful

How to create REST URLs without verbs? – Stack Overflow

February 10, 2012 by Brent Sordyl 0 Comments

General principles for good URI design:

Don’t use query parameters to alter state
Don’t use mixed-case paths if you can help it; lowercase is best
Don’t use implementation-specific extensions in your URIs (.php, .py, .pl, etc.)
Don’t fall into RPC with your URIs
Do limit your URI space as much as possible
Do keep path segments short
Do prefer either /resource or /resource/; create 301 redirects from the one you don’t use
Do use query parameters for sub-selection of a resource; i.e. pagination, search queries
Do move stuff out of the URI that should be in an HTTP header or a body

(Full Story: How to create REST URLs without verbs? – Stack Overflow)

restful, stackoverflow
,

Swagger: A simple, open standard for describing REST APIs with JSON

August 21, 2011 by Brent Sordyl 0 Comments

Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.

(Full Story: Swagger: A simple, open standard for describing REST APIs with JSON)

api, json, restful
, , ,

Migrating RESTful Transactions to OpenShift Express: Part 1 on Vimeo

August 14, 2011 by Brent Sordyl 0 Comments

Part 1 of two videos showing the process of how to migrate applications to the Red Hat OpenShift infrastructure. Part 1 describes the application and demonstrates how to deploy and run it locally. The application comprises two REST based services: a transaction coordinator which is deployed to a JBoss AS7 container and a simple service deployed into an embedded container. The client that interacts with the two services, written using javascript starts a transaction, makes transactional calls to two web services and then ends the transaction. Recovery from failures is also demonstrated.

(Full Story: Migrating RESTful Transactions to OpenShift Express: Part 1 on Vimeo)

cloudcomputing, jboss, restful
, , ,

How I became a REST ‘convert’

July 15, 2011 by Brent Sordyl 0 Comments

The third “leg” of the web services concept, Universal Description, Discovery and Integration (UDDI), conceptually makes a lot of sense, but in practice, hardly anyone uses it. As a developer, I couldn’t even think of a scenario where UDDI would help me in my particular project. Sure, I could artificially insert UDDI into my use case, but in the scenario where I needed loose coupling, I could get that by simply abstracting my end points and data schema. To the extent I needed run-time and design-time discoverability or visibility into services at various different states of versioning, I could make use of a registry / repository without having to involve UDDI at all. I think UDDI’s time has come and gone, and the market has proven its lack of necessity. Bye, bye UDDI.

(Full Story: How I became a REST ‘convert’)

restful, soa, soap
, , ,

RESTduino – Arduino hacking for the REST of us

April 22, 2011 by Brent Sordyl 0 Comments

This REST approach makes interfacing the Arduino to web applications elementary (a jQuery example is included) and most platforms provide basic HTTP out-of-the-box so integrating with desktop and mobile applications is very straightforward.

(Full Story: RESTduino – Arduino hacking for the REST of us)

restful
,

STREST Protocol – Streaming REST

April 14, 2011 by Brent Sordyl 0 Comments

STREST (Streaming and REST) Is a protocol which is meant to be simple, easy to understand and simple to implement both server and clientside. The protocol allows you to write controllers that can serve both normal REST request and response pairs and higher thruput STREST requests without any additional code. But the super awesomeness comes with the asynchronous nature, which allows easy firehose type streams as well as event callbacks.The protocol itself is virtually identical to regular HTTP packets, with the addition of a few additional headers. STREST utilizes a long running duplex connection where requests are all handled asynchronously. This allows it to be very high throughput. Because the packet is a fully formed HTTP packet it is possible to route it on the server side so that the same code can be used in STREST or regular REST.

(Full Story: STREST Protocol – Streaming REST)

restful, streaming
, ,

What is and isn’t REST

March 29, 2011 by Brent Sordyl 0 Comments

Things that aren’t magically true just because your API is RESTian:

  1. Writing clients is easy.You don’t even need a client, you can just derive everything from a single endpoint.
  2. Your API maps properly onto your business objects and therefore makes sense.
  3. Your API will scale properly.
  4. Your API is easy to extendYou won’t get support requests from people who didn’t read the documentation.

(Full Story: What is and isn’t REST)

restful

Dudes, this is so not REST

March 15, 2011 by Brent Sordyl 0 Comments

So it’s clear that Rdio’s “REST” API, like many other recent “REST” APIs such as DropBox’s*, isn’t REST at all. It’s more of an ad-hoc RPC scheme, which is ironic because there’s traditionally been a lot of enmity between REST proponents vs. those of RPC protocols like XML-RPC and SOAP. The SOAP boffins must be chortling behind their WSDLs at this

(Full Story: Dudes, this is so not REST)

restful

Apigee To-Go: Build, Skin, and Embed Your Own API Console

March 10, 2011 by Brent Sordyl 0 Comments

So today we’re launching Apigee To-Go, which lets you create your own API Console, skin it with the look and feel to match your brand, and then embed it where your developers are, on your own site or portal — for free.

(Full Story: Apigee To-Go: Build, Skin, and Embed Your Own API Console)

api, restful
,

RESTEasy tutorial

February 23, 2011 by Brent Sordyl 0 Comments

RESTEasy is an portable implementation of JAX-RS specification which provides a Java API for RESTful Web Services over the HTTP protocol. In this tutorial we will show a step-by-step guide how to create some simple RESTful Web services using Resteasy implementation.

(Full Story: RESTEasy tutorial)

jboss, restful
, ,
Older Entries

Follow

Get every new post delivered to your Inbox.