1. rolltop Search Result | BobVila.com

   ... Showrooms Featured: Sears - HVAC Repair. BobVila.com. Home. Login ... American Rolltop Desk. American Antique Rolltop Desk, rolltop desks, antique desk. ...

   www.bobvila.com/Search/?q=rolltop

2. rolltop Search Result | BobVila.com

   Featured: Appliance Repair & Shopping. View Showrooms ... American Rolltop Desk. American Antique Rolltop Desk, rolltop desks, antique desk. ...

   www.bobvila.com/Search/index.php?q=rolltop&sort=default&sort=default

3. Surface Mounted Rolltop Desk Lock Deals In-Store at Rockler Woodworking ...

   Great deals on Surface Mounted Rolltop Desk Lock at your local Rockler ... and Repair > Hardware & Building Supply > Surface Mounted Rolltop Desk Lock ...

   www.shoplocal.com/dl-47546218-surface-mounted-rolltop-desk-lock.fp

4. Vintage Hardware - ROLLTOP DESK LOCK KEY BLANK

   roll top rolltop desk key ... Keys " Brass Cabinet Locks & Skeleton Keys " ROLLTOP DESK LOCK KEY BLANK ... with double flag, typical of many rolltop desk locks. ...

   www.vintagehardware.com/index.php?cmd=product&prodid=26988

5. typewriter and fax machine repair

   Don's Office Products. Typewriter and Fax Repair. REPAIR. Enter content here. Enter content here ... Don's Office Products * 216 N. 5th street * Kingman * AZ ...

   www.donsofficeproducts.com/id67.html

6. Don's Office Products

   Provides photos and lists of office supplies and furniture, delivery options, and driving directions. ... We have been in business for over 25 years, and we ...

   www.donsofficeproducts.com

7. shh, don't startle the DRUNKEN HOUSEWIFE: the husband's desk

   ... an antique, child's rolltop desk in ill repair, with missing drawers, for ... He did some structural repairs. After all that, the desk was ready to refinish. ...

   www.drunkenhousewife.com/2006/10/husbands-desk.html

8. roll top desk repair

   Some years ago I purchased an attractive, massive, rolltop desk. ... Re: roll top desk repair (views: 2941) AHandyman -- Tuesday, 9 March 1999, at 2:02 p.m. ...

   ahandyman.com/cgi-bin/hmhelp.pl?read=295

9. Roll Top, Top Desk, Rolltop Desk, Oak Roll

   Solid Oak Amish Made Rolltop Desk Custom Finish. 1,550.00. FURNITURE HARDWARE REPAIR ROLL TOP DESK LOCK M1801. 15.50. Antique Roll top Desk Oak Child's ...

   www.munchk.net/rolltopdesk.html

10. Re: Tambour roll top desk repair

    Date: 11/5/5 22:56. In Response To: Tambour roll top desk repair (Judy Day) I have an antique rolltop desk which the tambour slats have broken away from the ...

    antiquerestorers.com/cgi-bin/bbs/furn/config.pl?read=8178

11. Tambour roll top desk repair

    I have a rolltop desk in which the tambour has ripped in between the wood slats in two areas. ... Tambour roll top desk repair. Judy Day (cache-rtc-ab01.proxy. ...

    antiquerestorers.com/cgi-bin/bbs/furn/config.pl?read=9150

12. Amish Mini Rolltop Jewelry Desk - Amish Furniture

    Some customization is available on the rolltop desks in our Holmes Office Collection. ... year after its delivery, we will repair or replace the piece at no ...

    www.dutchcrafters.com/product.aspx?intprodid=3366

13. Amish Deluxe Rolltop Desk - Amish Furniture

    Holmes Office Collection > Holmes Office Desks. Amish Deluxe Rolltop Desk ... first year after its delivery, we will repair or replace the piece at no cost to ...

    www.dutchcrafters.com/product.aspx?intprodid=3369

14. www.alan.net/prgshow/bobktambour.html

    This 1890's oak rolltop desk was in need of some. extensive repair. ... section of the desk, writing surface and drawer cases. There have been questions in ...

    www.alan.net/prgshow/bobktambour.html

15. www.alan.net/prgshow/idahomarkrolltop.html

    How do you repair the canvas backing of the tambour of a rolltop > desk when there are one or two splits between the tambours? IdahoMark replies: Hi DanC, ...

    www.alan.net/prgshow/idahomarkrolltop.html

16. Pete Cronin

    Pete started well and windmill repair business that kept him occupied. ... bought a large rolltop desk and converted it into a watch and clock repair desk. ...

    www.kansasheritage.org/medicine/isabel/fh_cronin.html

17. Antique Rolltop desk--Huge!

    I recently acquired my dads antique rolltop desk. This thing is enormous! ... will be taking the computer to the repair shop Monday so if its after that It'll ...

    www.antique-shop.com/forums/index.php?topic=891.0

18. Handyman Forum - Free Registration! - - rolltop desk

    Anyone know how to build a rolltop desk or the products needed? ... so I can fit a 19inch monitor in it all the desks I see online are way too small...

    www.handyman.com/forum/topic.asp?TOPIC_ID=2192

19. Mike Brown Auctioneer:upcoming auctions

    ... glass upper doors, S rolltop desk in need of repair, ornate walnut dresser ... desks, sewing machines, quilt rack, modern love seat, Windsor style desk chair, ...

    www.mikebrownauctioneer.com/auctions/120906Treftz/120906.html

20. The Wood Works Inc. - Porfolio: Desks, Small

    Finish Repair Portfolio. Repair Quik Quotes. Furniture ... STUDENT ROLLTOP DESK. Brown. Brown. Brown. Carlsen. Carlsen. Sternshein. TONED FINISH. Cross ...

    www.thewoodworksinc.com/portfolio/students.html

21. Amish Computer Rolltop Desk Amish Furniture

    Amish Holmes Office Collection >> Holmes Office Desks. Amish Computer Rolltop Desk ... year after its delivery, we will repair or replace the piece at no cost ...

    www.amishdiningroom.com/product.aspx?intprodid=3356

22. MyThings - View Item: Antique Rolltop Desk circa 1900

    MyThings Organize receipts and declutter your life ... Repair. Downloads. Valuations. Donate. Insurance. Report it stolen. Valuation. Collectibles ...

    www.mythings.com/viewitem.aspx?itemid=420716

23. MyThings - courtreporter's valuables

    Repair. Downloads. Valuations. Donate. Insurance. Report it stolen ... 1928 Smith Premier Rolltop Desk. 1928 Smith Premier Walnut Victorian rolltop desk. ...

    www.mythings.com/portfolio.aspx?userid=33233

24. Antique Appraisals and Online Valuations Ranging From Furniture to Car ...

    antique mahogany c-top rolltop desk w/ marble inlay and brass knobs. Date/Era/Period: ... would not be consistent with what we usually see on roll-top desks. ...

    wiw2u.com/index.cfm?fuseaction=appraisal.certificate&item_ID=164765

25. The Bicycle Shop

    ... showroom is a little cubicle with an oaken rolltop desk the Wrights' office. ... The Wright brothers' rolltop desk. Back along the hallway is the repair room. ...

    www.first-to-fly.com/Adventure/Expeditions/the_bicycle_shop.htm

26. desk

    Rolltop Desk with lots of pigeon holes and small drawers also ... several knockdown desks , office chairs, some in good shape, some need repair. I will sell...

    www.olx.com/q/desk/c-228/p-6

27. Ashley Furniture Reviews and Complaints - Rolltop Desk

    Ashley Furniture - Consumer reviews on Rolltop Desk ... to the person who sets up repairs on installment prolbems and sure enough, Joe ...

    www.my3cents.com/productReview.cgi?compid=579&product=Rolltop+Desk

28. Ashley Furniture Consumer Reviews

    Repair services. Delivery. Communication. Product quality ... Rolltop Desk (2) Sofa (2) Sofa & Loveseat (2) Sofa and Chair & (2) Sofa/loveseat/dining (2) ...

    www.my3cents.com/companyOverview.cgi?code=579

29. Yahoo! Groups : Search Results

    Desk has a large rolltop cover with computer side hutch, lateral file drawer, ... Computer Rolltop Desks and Computer Armoires are our Specialty. ...

    groups.yahoo.com/search?query=Desk+Tops+With+File+Cabinets

30. The Furniture Guys - Books

    ... varnishing, upholstering, basic repairs, and troubleshooting touch ... pine Hoosier, a Victorian throne chair, a rolltop desk, a pine hatrack, and more. ...

    www.furnitureguys.com/books.php

31. Lee's Summit Web - Bulletin Board - New Post

    Forums - For Sale, Buy or Trade also Garage Sale Notices - Rolltop Desk for sale - New Post ... chair needs some repair, otherwise in good condition. Best ...

    www.websitetoolbox.com/tool/post/lsmo/printadd?id=246210

32. Weber's - Furniture & Mirror Restoration

    Please click image to enlarge. Beautiful Oak Rolltop Desk ... Stripping | Repairs and Finishing | Mirror Resilvering | Photos | Contact Information ...

    www.webersfurniture.com/photos4.html

33. REPAIR or REPLACE tambour on rolltop desk? Recently purchased a rolltop ...

    Recently purchased a rolltop desk... tambour has a 5x3-inch hole drilled through it near the top. ...

    answers.yahoo.com/question/index?qid=20071007175048AALDQIK

34. furniture repairs/roll top desk? I need a replacement for the cover on ...

    That material is called tambour. Here is one link, but you can search the web ... That material is called tambour. Here is ... http://www.nationalproducts.com ...

    answers.yahoo.com/question/index?qid=20070411183754AA9jneI

35. HSA Cabinets for Consoles, RollRacks & Classic Racks

    Repair - Recone. Repair Policy. Repairs Shipping Form. DIY_Help. Pro Sound ... All HSA rolltop desks come equipped with upper and lower tambour locks for added ...

    www.prosoundservice.com/HSA.html?i708397:page=2

36. Buy Gold--Before They Sell Out

    ... old rolltop desk had a secret compartment and when disassembled for repair, a ... unsure whether he reported it to the owner of the rolltop desk. Would you? ...

    www.strike-the-root.com/4/herman/herman15.html

37. Dotta Auction-Auction Page

    ... desk, camelback and flattop trunks, yarn winders, antique oak "S" rolltop desk ... some items in need of some repair and other pcs. that are in good ...

    www.dottaauction.com/auction.php?id=127&type=mt

38. J. Rickford's Gallery 1

    1. 1890s Rolltop Mahogany Desk. Before and after. Nostalgic repairs and restoration. Not for the ... Our repairs, restorations and mending cover many, ...

    www.rickford.com/galler01.htm

39. Artifacts Furniture - Desk Hardware

    Keyhole - Roll Top Desk Escutcheon. Rolltop Desk Escutcheon. Brass. Units: Each ... Repairs & Restorations. Conversions. Upholstery. Customer Login. Username ...

    hardwarepast.com/index.php?...&category_id=8&Itemid=58&vmcchk=1

40. Cool Concept Cars Of The Past - AOL Autos

    Auto Repair. Video. Community. Car Loans. Insurance. Warranty. Auto Shows ... up like the cover of a rolltop desk," as one automotive writer that year put it. ...

    autos.aol.com/gallery/cool-concept-cars-of-the-past

41. WebFetchGo.com - News Search: antique desk

    ... 8 a.m. at Ryan's Boot & Shoe Repair, and Mike Ryan has already tied his apron ... Antique Writing Desks. Wooden Desks. Antique Rolltop Desks. Office Desk Antique ...

    www.webfetch.com/uk.webfetch/search/news/antique+desk

42. Victorian Walnut Engraved Rolltop Desk - eBay (item 330255649334 end ...

    eBay: Find Victorian Walnut Engraved Rolltop Desk in the Antiques , Furniture , Desks , 1800-1899 category on eBay. ... considering the minor repairs needed. ...

    cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&...&ssPageName=WDVW&rd=1

43. For Sale

    ... pile and has been fully reconditioned with extensive repairs. ... ROLLTOP DESK ... century solid oak roll top desk manufactured by The Filley & Crane ...

    www.woodenrestorations.com/catalog.html

44. Mainly Minis Dollhouse Miniatures: Automotive Car Repair Tool Set

    For your dollhouse hubby! A complete set of tools for his ... Oak Rolltop Desk and Chair Set. 0 items. Notify me of updates to Automotive Car Repair Tool Set ...

    www.dollhouseminiatures.net/product_info.php?products_id=2869

45. eBay walnut desk, chippendale desk and secretary desk items on eBay ...

    1860's Desk, All Original As-Is for Repair A LOOKER! 6 $162.51. Pickup only: Free. 1h 15m ... ANTIQUE CUTLER OAK ROLLTOP DESK SECRETARY CUBBY TOP ...

    antiques.listings.ebay.com/Furniture_Desks-Secretaries_W0QQdfspZ32Q...

46. Advanced - Inspiration - Minwax.com

    Wood Maintenance & Repair. Specialty Products. Accessories. Projects ... Rolltop ... red oak, this stylish rolltop writing desk provides a great deal ...

    minwax.com/projects/advanced

47. Result of Antique Arts Search

    Antique Rolltop Desk, Laurel Ridge. American Antique Rolltop Desk, rolltop desk, antique desks. ... There are really no major repairs that I can see. The ...

    tias.com/...&searchText=desk&search.x=13&search.y=9&search=Search

48. Locks U-Repair

    ... everything you need to repair replace and improve your home. ... Full Mortise Rolltop Desk Lock Set. Brass selvedge is 5/8' x 3-1/8' and covers steel lock body. ...

    www.u-repair.com/rockler/locks.php

49. NWsource: Classified listings for used furniture, antiques, computers ...

    Computer services & repair. Domestic care & services offered. Domestic care ... Retro Rolltop Desk exc $399 obo CASH (206)726-6024 Posted 10/08 More details ...

    www.nwsource.com/classifieds/scr/search/?pid=999&cid=8697194

50. Rolltop Desk - by Ryan Corrigan | LumberJocks.com :: woodworking community

    This was the last project at school. It remains today as you see it in the ... ceiling tile repair 2 days ago. humor spot at Home Refurbers 3 days ago ...

    lumberjocks.com/projects/883

• Yahoo: http://developer.yahoo.com/maps/rest/V1/geocode.html
• Yahoo (without app-id): http://www.batchgeocode.com/lookup/
• Lookup for ZIP/Place only, but many more free services: http://www.geonames.org/export/web-services.html

Anyway, still needed to call the WS from Java, but thanks to google I found a solution quickly (http://xml.nig.ac.jp/tutorial/rest/index.html) and expanded it to my usecase:

[sourcecode language='java']
    private static String buildWebQuery(Map parameters) throws Exception {
        StringBuilder sb = new StringBuilder();
        for (Map.Entry entry : parameters.entrySet()) {
            String key = URLEncoder.encode(entry.getKey(), "UTF-8");
            String value = URLEncoder.encode(entry.getValue(), "UTF-8");
            sb.append(key).append("=").append(value).append("&");
        }
        return sb.toString().substring(0, sb.length() - 1);
    }

    public static String callRestfulWebService(String address, Map parameters) throws Exception {
        return callRestfulWebService(address, parameters, null, 0);
    }

    public static String callRestfulWebService(String address, Map parameters, String proxy, String port) throws Exception {
        return callRestfulWebService(address, parameters, proxy, Integer.parseInt(port));
    }

    public static String callRestfulWebService(String address, Map parameters, String proxy, int port) throws Exception {

        Proxy proxyObject = null;
        if (StringUtils.isNotBlank(proxy) && port > 0) {
            InetSocketAddress proxyAddress = new InetSocketAddress(proxy, port);
            proxyObject = new Proxy(Proxy.Type.HTTP, proxyAddress);
        }

        String response = "";
        String query = buildWebQuery(parameters);

        // More info: http://xml.nig.ac.jp/tutorial/rest/index.html
        URL url = new URL(address);

        // make post mode connection
        URLConnection urlc = null;
        if (proxyObject == null) {
            urlc = url.openConnection();
        } else {
            urlc = url.openConnection(proxyObject);
        }
        urlc.setDoOutput(true);
        urlc.setAllowUserInteraction(false);

        // send query
        PrintStream ps = new PrintStream(urlc.getOutputStream());
        ps.print(query);
        ps.close();

        // retrieve result
        BufferedReader br = new BufferedReader(new InputStreamReader(urlc.getInputStream(), "UTF-8"));
        StringBuilder sb = new StringBuilder();
        String line;
        while ((line = br.readLine()) != null) {
            sb.append(line);
            sb.append("\n");
        }
        br.close();
        response = sb.toString();

        return response;
    }
[/sourcecode]

With these few methods you can call any REST WebService with any parameters (as Map) and use a proxy per call. The code also takes care of right encoding of parameters. The result is a xml string, which can be processed by regexp in an easy way.

Greetz, GHad

Tune into my radio show this afternoon at 4pm EST. (Link on side of page)

This is a unique opportunity to listen to and particate in an interview where I will be talking with Christine Clifton, a Life Coach who coaches individuals dealing with Chronic Conditions and Pain, and to find out how to conserve your energy!  She calls it becoming a 'PowerPlant'!  I coach Women and Couples dealing with the effects on energy when facing the challenges of fertility treatments such as IVF or IUI.  Both Christine and I also experience chronic pain, through fibromyalgia and migraine respectively.  We are in unique position to really bolster and guide those who are looking to really take care of themselves to create the best outcome from infertility issues or just for life in general. Stress is a big energy drain, as well as so many other factors.. Tune in to hear our thought provoking show!

Listen to the archived podcast if you can't make it live!  We welcome any callers who have any questions or comments during the show.

'See" you on the air!

Energetically yours,

Coach Louise Crooks

A good screen cast walks you through the new tiered 'ACE' architecture which is designed around a top level 'Authority' a unit of geo-location which maps to an explicit DNS address eg:

brightsparc.data.beta.mssds.com

Under this Authority are Containers, and within a container is a series of Entities.  The flat structure is analogous to Tables and Rows, however a Row can represent different Kinds of data that doesn't necessarily conform to the same schema. In fact any data other then the core ID, Version and Kind attributes are 'Flexible Properties' and set similar to a key based dictionary.

Under the hood this functionality could well be implemented with the new Filtered Index and Sparse Column features of SQL 2008 which allow for efficient storage of such data.

SSDS is a web service accessed over the wire using a SOAP or simple REST interface currently secured with basic credentials over https.  To get started I recommend downloading the SDK to create / update and query your data using the explorer GUI.  In REST speak, use POST to create a record, PUT to update and record and DELETE speaks for itself.  Moving forward cloud computing security is a challenge for Microsoft, but will no doubt tie in with it's claim-based Card Space initiative.

Ryan Dun has a great blog with some examples of what is possible right now with SSDS, as well as very nifty open source REST library that can wrap POCO's for persisting them to the cloud.

Although I did experience some unexpected outage on the service, Microsoft do plan to charge for this service in the future so I'm sure they will be looking at SLA of at least two 9's if they are planning on competing with the likes of Amazon and Google.

• REST: http://en.wikipedia.org/wiki/Representational_State_Transfer, and http://ryandaigle.com/articles/2006/8/1/whats-new-in-edge-rails-simply-restful-support-and-how-to-use-it
• ExtJS: http://extjs.com/
• Jester: http://giantrobots.thoughtbot.com/2007/4/2/jester-javascriptian-rest

What is the idea? Hmm, let me explain it as simply as I can.

REST
The idea of REST is that a web service should simply provide resources ('things', or 'objects', that you can do things with, such as create and read and change), with a set of actions
(verbs, the things you can do with those objects). A typical RESTful
website will provide a set of related resources with a set of possible
actions for each of those resources. To a person the site will send
HTML, but to a machine it might send XML or JSON formatted data. The
actions that can be performed on these objects should the several verbs
of REST: post, get, put, and delete (these correspond to the more human
words create, read, update, and destroy, also known as CRUD).

ExtJS
The
idea behind ExtJS (as far as I can perceive) is to create a javascript
framework that makes it possible to script an application's entire
workings in the browser, with a rich look and feel. Do some google
searches to find examples of ExtJS in the works, or head over to the Ext Documentation for API and examples.

Jester
Jester
is a Javascript library that emulates Rails-style models. It could be
thought of as a Javascript ActiveResource. Specifically, it allows you
to access a Person object, for example, in your Javascript code.
Getting that object includes a transparent AJAX call to the
application's standard REST protocol, and it supports modifying those
objects and saving them, almost identical to the way you'd do it in
your Rails controllers.

The Synergy
My
point to this article is that I think the combination of these
libraries and concepts is the Right Way to do web programming (at least
with what we have at our fingertips this year). I believe it is the
Right Concept to execute all of the application-specific logic at the
client and leave the webserver as a dumb but robust resource operator.
(Bonus: Add slingshot to your application and this will work extremely well!)
The
coolness begins here. If you program your applications in this way, you
get a bonus: You can super-easily (well, okay, gui's can take a while
to make well) create several different client-side interfaces to your
application. You could create a multi-faceted application and create a
client interface that is specific to each facet of operations. Scale it
bigger and run several applications that are mostly different, all as
one integrated application, just with different client interfaces to
interact with only what is relevant to its needs.

Give me your thoughts!

jester, rails, rest, restful, rubyonrails

REST makes the architecture clear

Roy Fielding's concept of REST has focussed attention back to the web. If you really want to write a web application, you know what to do ..

• figure out what Resources you want to make manipulable via GET, POST, PUT and DELETE requests (i.e. CRUD operations)
• implement code which responds to those requests

OpenJPA (JPA) makes persistence easy

The Resources you want to make manipulable must of course be stored somewhere. Thanks to JPA (Java Persistence Architecture). Using Apache's OpenJPA could hardly be easier. You just define an entity in a plain old Java class with fields and getters and setters and annotate the class definition as @Entity. Once that is done, you persist instances of that class by passing them to a persist method of an EntityManager. Could it be simpler? JPA abstracts away database dependencies, so you no longer have to worry (much) about implementing your persistence layer differently for the different databases you want to support.

Jersey (JSR-311) makes request handling easy

So if you can store and retrieve Resources from the db with no problem, you just need code which accepts and interprets requests - figures out what resources are being asked for - and then marshals them back in responses. Well, anything which implements the JSR-311 API (such as the reference implementation from Sun Jersey, or Apache CXF ) makes that easy.

REST strictly refers to a collection of network architecture principles which outline how resources are defined and addressed. The term is often used in a looser sense to describe any simple interface which transmits domain-specific data over HTTP without an additional messaging layer such as SOAP or session tracking via HTTP cookies. These two meanings can conflict as well as overlap. It is possible to design any large software system in accordance with Fielding’s REST architectural style without using HTTP and without interacting with the World Wide Web. It is also possible to design simple XML+HTTP interfaces which do not conform to REST principles, and instead follow a model of remote procedure call. The difference between the uses of the term “REST” therefore causes some confusion in technical discussions.

Systems which follow Fielding’s REST principles are often referred to as “RESTful”.

Most introductions to REST start with the formal definition and background. I’ll defer this for a while and provide a simplified, pragmatic definition: REST is a set of principles that define how Web standards, such as HTTP and URIs, are supposed to be used (which often differs quite a bit from what many people actually do). The promise is that if you adhere to REST principles while designing your application, you will end up with a system that exploits the Web’s architecture to your benefit. In summary, the five key principles are:

• Give every “thing” an ID
• Link things together
• Use standard methods
• Resources with multiple representations
• Communicate statelessly

Let’s take a closer look at each of these principles.

The term REST was defined by Roy T. Fielding in his PhD thesis (you might actually want to follow that link — it’s quite readable, for a dissertation at least). Roy had been one of the primary designer of many essential Web protocols, including HTTP and URIs, and he formalized a lot of the ideas behind them in the document. (The dissertation is considered “the REST bible”, and rightfully so — after all, the author invented the term, so by definition, anything he wrote about it must be considered authorative.) In the dissertation, Roy first defines a methodology to talk about architectural styles — high-level, abstract patterns that express the core ideas behind an architectural approach. Each architectural style comes with a set of constraints that define it. Examples of architectural styles include the “null style” (which has no constrains at all), pipe and filter, client/server, distributed objects and — you guessed it — REST.

If all of this sounds quite abstract to you, you are right — REST in itself is a high-level style that could be implemented using many different technologies, and instantiated using different values for its abstract properties. For example, REST includes the concepts of resources and a uniform interface — i.e. the idea that every resource should respond to the same methods. But REST doesn’t say which methods these should be, or how many of them there should be.

One “incarnation” of the REST style is HTTP (and a set of related set of standards, such as URIs), or slightly more abstractly: the Web’s architecture itself. To continue the example from above, HTTP “instantiates” the REST uniform interface with a particular one, consisting of the HTTP verbs. As Fielding defined the REST style after the Web — or at least, most of it — was already “done”, one might argue whether it’s a 100% match. But in any case, the Web, HTTP and URIs are the only major, certainly the only relevant instance of the REST style as a whole. And as Roy Fielding is both the author of the REST dissertation and has been a strong influence on the Web architecture’s design, this should not come as a surprise.

Finally, I’ve used the term “RESTful HTTP” from time to time, for a simple reason: Many applications that use HTTP don’t follow the principles of REST — and with some justification, one can say that using HTTP without following the REST principles is equal to abusing HTTP. Of course this sounds a little zealous — and in fact there are often reasons why one would violate a REST constraint, simply because every constraint induces some trade-off that might not be acceptable in a particular situation. But often, REST constraints are violated due to a simple lack of understanding of their benefits. To provide one particularly nasty example: the use of HTTP GET to invoke operations such as deleting an object violates REST’s safety constraint and plain common sense (the client cannot be held accountable, which is probably not what the server developer intended). But more on this, and other notable abuses, in a follow-up article. (more)

Why REST?

REST-style services (i.e., RESTful services) adhere to a set of constraints and architectural principles that include the following:

Fielding writes that "REST-based architectures communicate primarily through the transfer of representations of resources" (Section 5.3.3). This is fundamentally different from the Remote Procedure Call (RPC) approach that encapsulates the notion of invoking a procedure on the remote server. Hence, RPC messages typically contain information about the procedure to be invoked or action to be taken. This information is referred to as a verb in a Web service request. In the REST model, the only verbs allowed are GET, POST, PUT, and DELETE. In the RPC approach, typically many operations are invoked at the same URI. This is to be contrasted with the REST approach of having a unique URI for each resource.

These are the basic principles behind REST. However, when people talk about the benefits of RESTful systems today, they usually are not strictly applying these principles. For example, among REST advocates, keeping shopping cart data on the server and maintaining a session related to the shopping process that is using the cart is acceptable. (Storing session information or shopping cart data on the server is a clear violation of Fielding's original REST concept since it violates the requirement that a service be stateless.) In fact, the XML/HTTP Binding provided by JAX-WS for implementing RESTful services provides for session management capabilities using cookies, URL rewriting, and SSL session IDs.

More significant deviations from Fielding's definition of REST involve getting around the "uniform interface" constraint by embedding verbs and parameters inside URLs. The Amazom.com REST interface, for example, includes verbs in query strings and doesn't have unique URIs for each resource. Systems like this, although labeled as RESTful, are really starting to look very much like RPC using XML over HTTP without SOAP.

For the purposes of this book, I am not going to wade into a debate on what is or isn't RESTful. I simply define RESTful Web Services in contrast to SOAP Web Services. Table 3–1 illustrates the principal differences. (more)

What are the differences among SOAP, XML-RPC, and REST?

EXPERT RESPONSE FROM: David Linthicum

SOAP, or Simple Object Access Protocol is an XML-based object invocation protocol, and was originally developed for distributed applications to communicate over HTTP. SOAP defines the use of XML and HTTP to access platform independent services.

In contrast, XML-RPC is a Remote Procedure Calling protocol that works over the Internet, and is really an XML-RPC message that is an HTTP-POST request. The body of the request is in XML. A procedure executes on the server and the value it returns is also formatted in XML.

* REST is a bit different. REST (REpresentative State Transfer) is a technique for implementing Web services using XML documents plus standard HTTP, using its well-known operations (PUT, GET, POST, DELETE). The service-specific API is created by defining URIs (typically URLs) and XML documents that model the data structures and requests/responses required. REST has some very useful properties, e.g. you can use standard firewalls for security, standard caching for performance, while still letting you do everything that SOAP and XML-RPC can do.

ReST Vs SOA(P)

[slideshare id=82630&doc=rest-vs-soap-yawn2289&w=425]

[slideshare id=114108&doc=web-of-science-rest-or-soap4736&w=425]

REST Applied to URI

Uniform Resource Identifiers (URI) are both the simplest element of the Web architecture and the most important. URI have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers, and finally the combination of Uniform Resource Locators (URL) and Names (URN). Aside from its name, the URI syntax has remained relatively unchanged since 1992. However, the specification of Web addresses also defines the scope and semantics of what we mean by resource, which has changed since the early Web architecture. REST was used to define the term resource for the URI standard, as well as the overall semantics of the generic interface for manipulating resources via their representations.

• Redefinition of Resource
• Manipulating Shadows
• Remote Authoring
• Binding Semantics to URI
• REST Mismatches in URI

REST Applied to HTTP

The Hypertext Transfer Protocol (HTTP) has a special role in the Web architecture as both the primary application-level protocol for communication between Web components and the only protocol designed specifically for the transfer of resource representations. Unlike URI, there were a large number of changes needed in order for HTTP to support the modern Web architecture. The developers of HTTP implementations have been conservative in their adoption of proposed enhancements, and thus extensions needed to be proven and subjected to standards review before they could be deployed. REST was used to identify problems with the existing HTTP implementations, specify an interoperable subset of that protocol as HTTP/1.0, analyze proposed extensions for HTTP/1.1, and provide motivating rationale for deploying HTTP/1.1.

The key problem areas in HTTP that were identified by REST included planning for the deployment of new protocol versions, separating message parsing from HTTP semantics and the underlying transport layer (TCP), distinguishing between authoritative and non-authoritative responses, fine-grained control of caching, and various aspects of the protocol that failed to be self-descriptive. REST has also been used to model the performance of Web applications based on HTTP and anticipate the impact of such extensions as persistent connections and content negotiation. Finally, REST has been used to limit the scope of standardized HTTP extensions to those that fit within the architectural model, rather than allowing the applications that misuse HTTP to equally influence the standard.

• Extensibility
• Self-descriptive Messages
• Performance
• REST Mismatches in HTTP
• Matching Responses to Requests

RESTful Web Services

This chapter describes the REST architecture and RESTful web services, and explains how to use the REST API to create RESTful web services.

What Are RESTful Web Services?

Representational State Transfer (REST) is a software application architecture modeled after the way data is represented, accessed, and modified on the web. In the REST architecture, data and functionality are considered resources, and these resources are accessed using Uniform Resource Identifiers (URIs), typically links on the web. The resources are acted upon by using a set of simple, well-defined operations. The REST architecture is fundamentally a client-server architecture, and is designed to use a stateless communication protocol, typically HTTP. In the REST architecture, clients and servers exchange representations of resources using a standardized interface and protocol. These principles encourages REST applications to be simple, lightweight, and have high performance.

RESTful web services are web applications built upon the REST architecture. They:

• expose resources (data and functionality) through web URIs
• use the four main HTTP methods to create, retrieve, update, and delete resources

RESTful web services typically map the four main HTTP methods to the so-called CRUD actions: create, retrieve, update, and delete. The following table shows a mapping of HTTP methods to these CRUD actions.

Table 6-1 HTTP Methods and their Corresponding CRUD Action

(more)

Putting REST on Rails

"Convention over configuration" is one of the key principles behind the design of Ruby on Rails. It was built with a specific way of doing things and as long as you follow the "Rails way" everything will just work with little or no configuration. That's part of the reason Rails is so successful--as long as you follow its conventions you get many benefits with less work than other frameworks that require you to be more explicit.

The HTTP protocol is very similar in this respect. Stray from the path and you'll find yourself hacking together replacements for basic things HTTP gives you for free. Stay on the path and you gain benefits like caching and better scalability of your applications with less effort. A well-designed--which typically means a RESTful--web application makes good use of available HTTP methods, rather than relying on GET requests to trigger server state changes.

The ideal is to dispatch to a different handler based on the HTTP method, actually running different code depending on the method, and making it impossible to unintentionally change state with a GET request.

(more)

Getting Started with RESTful Rails

Since DHH's keynote at RailsConf there has been a lot of talk about RESTful rails. I finally decided to get up to speed and start exploring. This is a look at the new scaffold_resource and routing that will be in Rails 1.2.

The Rails application is a sort of "jukebox" or more accurately a list of artists and their albums. But enough about the name, let's get started. (more)

Online REST Web Service Demo

This online demo is an example of a RESTful Web Service. The service was implemented using the principles of the REpresentational State Transfer architectural style. It exposes the Hypersonic sample database as Web Service.
Using HTTP and XML, resources can be queried, removed and altered. A Web browser like Firefox or MS Internet Explorer can be used for queries. (more)

NetBeans REST Web Services, Building and Deploying

[wikipedia.org]
[http://www.webreference.com]
[http://www.infoq.com/]
[http://tssblog.techtarget.com/]
[http://developers.sun.com]
[http://www.slideshare.net/]
[http://railsforum.com/]
[http://searchsoa.techtarget.com/]
[http://www.thomas-bayer.com/]

When I read articles related to REST, RESTFul, and Web Services, most of contents support one side of these. Why don’t we use in mix? There are places that are very good for REST, and some others are not. For example, REST can cover all resource oriented processing, but it cannot cover business oriented processing such as “verify”, “process”, etc. When you need to access to a public API, which is made in Web Services, you have to use it. I think we should be flexible as IT architect. How come so many IT architects tend to have naive mind？(Another similar example, JBI vs SCA arguments, EJB or not EJB, etc.)

REST, RESTFul、そして、Web Services関係の記事を読む時、とかく一方的な意見に出会う。どうして混ぜて使えないのか？RESTにとっていいところもあるし、良くないところもある。たとえば、RESTは、リソースの処理は得意だけれど、ビジネス処理は不得意。たとえば、あってるか間違ってるかとか、ステイタスを変えるとか。公共に使われているAPIは、Web Servicesでできているかもしれない。その時は、それしか使えない。IT設計者としては、柔軟性が求められる。どうして、多くのIT設計者は、単純思考なのかな？似たようなこととして、JBIとSCAの議論とか、EJBを使うか使わないかとか。

They have timed their market entry well given Twitter's very public performance woes.  But GNIP offers the possibility of returning aggregated data in a consistent way, so may help speed up the standardization of the various microformats out there on the social web.

I like GNIP because of it's simple RESTful approach to design and architecture.  Their V1 was built in 90 days, and followed up with transitioning the system into the cloud care of AWS/Ec2 running on top of TerraCotta and ActiveMQ.  Very cool!

E' un po' che mi chiedo se "dietro" una risorsa si possa "nascondere" qualcosa di più "complesso" (una serie di passi, ad esempio, una logica applicativa complicata a piacere, ecc.), continuando, però, a soddisfare i vincoli di REST (mi riferisco, sopratutto, all'interfaccia uniforme e alla mancanza di stato).

Stefan Tilkov, autore dell'articolo "Addressing Doubts about REST" (già citato in un articolo precedente "Letture consigliate su REST"), spiega come REST (REpresentational State Transfer) non sia confinato alle sole operazioni CRUD (Create, Read, Update and Delete): una URI tipo http://example.com/calculation?a=2&b=3, infatti, può corrispondere alla somma tra a e b. L'articolo descrive una soluzione in sintonia con REST (implementato con HTTP): una POST che abbia come effetto la creazione della risorsa-risultato e come ritorno la URI corrispondente (da usare con una GET).

Il libro "RESTful Web Services" di Leonard Richardson e Sam Ruby, nella parte dedicata al disegno di risorse, illustra strategie simili.

Quindi dietro una risorsa si può celare qualcosa di più "complesso" di una "semplice" entità. Tale risorsa, però, non coincide con la risorsa-risultato cercata, è il punto di raccolta delle richieste ("RESTful Web Services" lo definisce factory): accoglie i POST (richiesta di creazione, non sicura, non idempotente), crea la risorsa-risultato (o ne accoda la richiesta) e ne ritorna l'URI da usare con una GET (richiesta di informazioni, sicura, idempotente).

Questo, che sicuramente rispetta i vincoli imposti da REST, mi sembra, oltre che macchinoso, richiedere al client una certa "consapevolezza" (che, in taluni casi, potrebbe rafforzare l'accoppiamento): alla POST deve seguire necessariamente una (o più) GET con cui recuperare la risorsa-risultato (o richiederne lo stato di esecuzione - in tal caso il client deve farsi carico anche di una DELETE per eliminare la risorsa temporanea). Conseguenza dell'interfaccia uniforme (i metodi con semantica indipendente dalle risorse sono generici, non specializzati e, talvolta, impongono al client di soddisfare un flusso di lavoro ben preciso) e della mancanza, per alcune situazioni, di soluzioni REST collaudate.

Un codice 201 ("Created"), in risposta alla POST, che oltre alla URI della risorsa creata riportasse la sua rappresentazione, o un codice 303 ("See Other") che "inviterebbe"  ad eseguire "automaticamente" una GET verso la URI ritornata (la risorsa-risposta), potrebbero isolare la logica di business del client dalle logiche del colloquio HTTP; sono soluzioni, comunque, da studiare di volta in volta.

----><----

Hai trovato questo post interessante? Segui il feed e commenta!

La presentazione definisce i concetti architettura software (astrazione degli elementi di run-time di un sistema, durante una delle sue fasi operative) e stile (insieme di vincoli che inducono le qualità e i compromessi di un'architettura) e indica quali vincoli caratterizzano lo stile di architettura denominato REST:

• mancanza di stato (ha qualità di migliorare la scalabilità, l'affidabilità e la visibilità - circoscrivendo la richiesta - ma ha come compromessi il degrado delle prestazioni - a causa del maggior numero di dati da presentare - e il legame più stretto tra client e server)

• client-server (separa le competenze e migliora la scalabilità)

• caching (migliora l'efficienza e la scalabilità ma riduce l'affidabilità - i dati in cache potrebbero non essere aggiornati)

• interfaccia uniforme (migliora la visibilità, semplifica e disaccoppia ma riduce l'efficienza - a causa della generalizzazione)

• gerarchia a livelli (introduce l'incapsulamento e l'intermediazione, semplifica i client ma aumenta la latenza)

• codice on-demand (download ed esecuzione di applet e script: semplifica i client, aumenta le possibilità di estensione ma riduce la visibilità)

Spiega poi in dettaglio il vincolo di "interfaccia uniforme":

• tutte le risorse sono identificate da URI

• i metodi hanno semantica indipendente dalle risorse

• i messaggi scambiati (rappresentazione delle risorse) sono auto-descrittivi

• le rappresentazioni indicano lo stato della risorsa, gli eventuali link presenti le transizioni possibili

Elenca infine i benefici di REST:

• scalabilità

• semplicità

• minimo accoppiamento

Vale la pena - lo sto facendo - leggersi la tesi (pubblicata anche come pdf).

[slideshare id=356791&doc=200804restapachecon-1208367700049034-9&w=425]

----><----

Hai trovato questo post interessante? Sottoscrivi il feed completo e partecipa alla discussione

I punti più stimolanti:

• il modello publish-subscribe è implementabile con i feed RSS o Atom: i sottoscrittori interrogano per nuovi messaggi. Non è la soluzione quando il ritardo deve essere minimo

• se si decide per XML si può usare XML Schema per definire formalmente i messaggi e il data binding per generare le classi

• l'accoppiamento blando e le transazioni ACID non vanno d'accordo: dover coordinare il commit tra sistemi diversi rafforza l'accoppiamento

• l'asincronia si può implementare come una risposta 202 (Accepted) o 201 (Created) ed una URI nel messaggio di ritorno

Concludo riportando che entrambi concordano nell'affermare che REST non poi così semplice e che per alcune cose mancano soluzioni standard.

----><----

Hai trovato questo post interessante? Sottoscrivi il feed completo e partecipa alla discussione

CRUD means Create-READ-UPDATE-DESTROY.

You might heard about HTTP verbs, GET, POST. In REST, they add 2 new verbs, i.e, PUT, DELETE.

There are 7 default actions, those are - index, show, new, create, edit, update, destroy

GET is used when you retrieve data from database. POST is used when you create new record in database. PUT is used when you are updating any existing record in database, and DELETE is used when you are destroying any record in database. Following table may clear the concept.

Action VERB

index                        GET

show                        GET

new                          GET

create                       POST

edit                          GET

update                      PUT

destroy                    DELETE

• mixwit.com/username/best-of-the-80s-mix

As mentioned before, we're updating urls on Mixwit. This was part 2 of the changes. No more ugly 32-character codes! A few extra things to note:

• Your old urls/links will continue to work! No dead links here, folks.
  
• The url will be based on your current title and can't be changed (for now). If you change the title of a mix, your mix and page will display the new title, but the URL will be the same (to prevent dead links).
• Foreign characters will change. Accented characters will lose accents, and double-character fonts (i.e. Chinese) simply get eliminated.
• If there's no title, we simply assign "mix" as the URL (mixwit.com/user/mix).
• If there's more than one of the same name, we add and number count after the title (mixwit.com/user/mix-2).
• Anonymous users still get the old, ugly urls.
• We'll make the urls editable in the near future.

OH... MY.... I'm excited.

I know just enough to know I wanted to come to the session titled ""Future of Fellowship One API: Moving to a RESTful architecture"

can I say it again? OH. MY.

Standards are cool. I now understand why Steve Smith is so big on this stuff. It makes pulling the info you want dead simple. Nick Floyd (that's a fuzzy representation of him on the right) presented and WOW he was excited about this stuff. I started imagining what I could do with what little I understood of what he was explaining, and now I'M excited. This is some big stuff kids. Big stuff.

 It is my pleasure to to introduce you to the Auckland Connected Systems User Group. This is a new .NET User Group in Auckland, New Zealand. The meetings will be held at Datacom and at Microsoft (our sponsors), we try to meet once every two months unless we have an impromptu speaker. The technologies covered will be around BizTalk, WCF, WF and any other integration technologies from Microsoft.

  If you are interested please check out the website and subscribe to the newsletter or subscribe to the News RSS feed to learn about upcoming meetings. You can also join the user group as we might add sponsor offers and member downloads in the future after meetings.

  To kick it off in a big way our first meeting details are below:

  Event: Creating and Consuming RESTful Web Services with WCF - Ron Jacobs

  Description: RESTful Web services are emerging as a new way to make your web service available to even the simplest of client apps. Learn how to design, build, create and consume these services with WCF.

  About Ron Jacobs:
  Ron Jacobs is a Sr. Technical Evangelist in the Microsoft Platform Evangelism group based at the company headquarters in Redmond Washington. Ron's evangelism is focused on Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF). He is also the former host of the ARCast series on Channel 9 about IT Architecture.

  Date:
 Frida, 23 of May 2008 5:30 p.m.

  Location:  

 MPC Room
 Microsoft New Zealand
 Level 5, 22 Viaduct Harbour Avenue
 Auckland, New Zealand 1010

 Please register for the meeting by filling out your details on the meeting page.

I fell asleep just after 3 am and I was out like a light. Around 7:30, I started waking up, but once I saw the time, I passed out again.

At 10, I woke up to make a call and started my day. So far, my day has consisted of laundry. My Wife & I are heading out tonight to a classy event.

We will be attending "An Evening With Salman Rushdie". He's an extremely contreversial author that wrote The Satanic Verses.

To be perfectly honest, I don't really know that much about him. She won the tickets so I decided to go with her. I'm mostly going to this in order to be seen by Ottawa's elite. It sounds snobby, but I think it's good to get cultured and see/meet people that you wouldn't normally get to see.

My Wife surprised me by buying me floor lamps for my newly designed bedroom. After that, we "baptised" my new bed.

Yep, we're classy folks.

Stay classy, Blog fans.

En el web 2.0 el visor tiene una especial importancia. El fundamento tecnológico del web 2.0 se basa en el “web as platform”, es decir, se pretende que el visor se convierta en un interfaz de acceso universal. Así, idealmente el visor debería sustituir al sistema operativo. A través del visor deberíamos de ser capaces de acceder a cualquier servicio. Google es un claro ejemplo en este sentido, ya que nos pone gran cantidad de servicios accesibles a través del visor como son: GoogleMaps, GoogleDocs, Gmail…

Para hacer posible este avance hacia un visor universal, el web 2.0 se apoya en una serie de componentes. Estos componentes son el URI (para el direccionamiento), el protocolo HTTP, un lenguaje abierto para la representación de los recursos y las aplicaciones web, que no son más que programas que se pueden ejecutar en nuestro visor. Antes de seguir, aclarar que por recurso entendemos cualquier cosa en Internet que merezca la pena ser referenciada. Un recurso puede ser un fichero, una foto, un video… siempre y cuando éste sea accesible a través de una dirección (URI).

Llegados a este punto, es importante resaltar el cambio de concepción del web 2.0 respecto al web tradicional o web 1.0. El web tradicional se limitaba a representar documentos, mientras que en el web 2.0 se representan recursos y se ejecutan aplicaciones. En el web 2.0 se apuesta por la interactividad.

Con el tiempo, hemos pasado del concepto de web humana al de web programable. Si, en un principio, teníamos un web construido exclusivamente para la visualización de contenido por parte de las personas, en la actualidad, tenemos un web donde los recursos deben ser legibles tanto para las personas como para otras aplicaciones. Este cambio ha supuesto inexorablemente la aparición de formatos abiertos de representación de recursos como son XML, XHTML (fusión entre XML y HTML)…

No solo la aparición de los formatos abiertos de representación de recursos han sido la base para el desarrollo del web 2.0. También, otras aplicaciones ya presentes desde el inicio de Internet como el protocolo HTTP han posibilitado este cambio hacia el web 2.0. Este protocolo transaccional fue diseñado, en un principio, pensando en la web humana. Sin embargo, la capacidad de direccionamiento, el que sea un protocolo sin estados y que soporte la optimización de tráfico han hecho que la nueva concepción del web haya podido sustentarse sobre este protocolo.

Es interesante ver como a través de HTTP sobre la arquitectura REST, la web programable es un hecho. RESTful (Representational State Transfer) es una arquitectura diseñada por Roy Fielding, quien fuera uno de los desarrolladores del protocolo HTTP. Aunque REST no fue diseñada especialmente para HTTP, si lo fue pensando en este protocolo. No es la única arquitectura propuesta en el sí de lograr la web programable, pero sí es la única que se utiliza en aplicaciones reales. En REST se apuesta por los siguientes principios:

• Recursos identificables: todos los recursos deben ser accesibles (permalink).
• Interfaz de acceso uniforme: se basa en las siguientes acciones: create, read, update y delete.
• Comunicación sin estado: principio que aporta escalabilidad.
• Representación de los recursos: XML, XHTM…
• Hypermedia: la navegación debe basarse en enlaces.

1. Now we have OpenID authentication on SPhred, i.e., new users do not need to Sign Up to use SPhred if they have an Open ID account.
2. In the past, some users have suggested that they do not want their full name to be shown on their profile page, so now we do not show any user's full name anywhere because we have added nicknames or user names.
3. I thought its a bit tedious to type your whole email address to login, hence added an option of using the Sign In name, ie. you can either use your Sign In name or the email address. If you do not know your Sign In name yet then Sign In using your email address and you will see it once you are signed in.
4. If you have done some activity on SPhred like adding tags to your profile, SPhredding, connected with other people then SPhred can also recommend a network of people with similar interests on SPhred. Simply go to your profile and click on the 'More Like you' link to check this out.
5. You can also send short messages to other users by using the 'Buzz' link on a user profile.
6. I think it is important to bring the old posts back to users' attention once in a while even if it has gone past 10th page and hence have implemented a 'Random Picks' widget which is shown on almost every page. Go to the widgets page