DJ Adams

Blog posts tagged "http"

  1. Obtaining auth code grant type OAuth 2.0 tokens for Google APIs with a script

    Writing a script to obtain OAuth 2.0 bearer tokens for Google API calls using the auth code grant type.

  2. CAP, CORS and custom headers

    Digging into CORS support in CAP, covering CORS headers, preflight requests and custom header handling.

  3. OData query operations and URL encoding the system query options with curl

    Using curl to send OData query operations with system query options that contain whitespace, letting curl handle the URL encoding.

  4. curl and multipart/form-data

    Discovering how curl handles multipart/form-data including reading from standard input.

  5. Monday morning thoughts: local http servers and containerisation

    I look back on an idea surfaced by a hero of mine, and think about how that idea laid the path for today's containerisation initiatives.

  6. UI5 - looking back and forward

    30 Days of UI5 - day 26 by DJ Adams.

  7. New Omniversity Course Video!

    Releasing a new video for my Web Programming with SAP's Internet Communication Framework course.

  8. Making OData from SAP accessible with the ICM's help

    Using the SAP Internet Communication Manager to make OData from NetWeaver Gateway more accessible.

  9. SAP ICF course marketing: video!

    Creating a marketing video for my SAP ICF course at the Omniversity.

  10. Web Programming with SAP's ICF: new course dates

    Announcing new dates for my Omniversity course on Web Programming with SAP's Internet Communication Framework.

  11. Stand steady on the shoulders of giants

    Making the case for attending my Omniversity course on Web Programming with SAP's Internet Communication Framework.

  12. Scratching an itch - Magic The Gathering card info

    Scratching an itch by building a quick tool to look up Magic The Gathering card information.

  13. REpresentational State Transfer (REST) and SAP

    Exploring how REST as an architectural style applies to SAP integration scenarios.

  14. REST orientation - Controlling access to resources

    Auth with respect to the alternative dispatcher layer in ABAP.

  15. A new REST handler / dispatcher for the ICF

    One of the best underlying mechanisms to be introduced into the Basis / NetWeaver stack in the past few years is the Internet Communication Framework (ICF), which is a collection of configuration, interfaces, classes and a core set of processes that allow us to build HTTP applications directly inside SAP.

  16. SAP and Google Wave - Conversation Augmentation

    Demonstrating integration between Google Wave and SAP, inspired by the Dashboard project from six years earlier.

  17. Command lines of the future, and simplicity of integration

    Thinking about chat-style interfaces as command lines of the future and their implications for integration.

  18. Coffeeshop screencast: HTTP conneg, resource representations and JSON

    Showing HTTP content negotiation, resource representations and JSON support in coffeeshop.

  19. 2nd coffeeshop REST/HTTP screencast

    Recording a second coffeeshop screencast highlighting its REST-orientated HTTP-based pubsub nature.

  20. Google Wave, XMPP and complexity

    Considering the complexity of Google Wave and XMPP versus the incremental approach of the web.

  21. Webhooks postbin example for Coffeeshop

    Demonstrating webhooks with coffeeshop using the PostBin developer utility.

  22. First coffeeshop demo screencast

    Recording a screencast demonstrating some of the basic features of my coffeeshop pubsub project.

  23. 'Coffeeshop' - lightweight HTTP-based pubsub

    About a lightweight, REST-orientated HTTP-based publish/subscribe implementation that I’ve been working on for the last few days.

  24. Tarpipe REST connector in 5 minutes

    Demonstrating the new Tarpipe REST connector with a quick five-minute example.

  25. Twitter's success

    Thoughts on messaging, microblogging, and Twitter's success.

  26. An HTTP connector for Tarpipe: 'tarbridge'

    Building tarbridge, an HTTP connector for Tarpipe that enables POST requests to arbitrary URLs.

  27. Forget SOAP - build real web services with the ICF

    I don’t like getting into a lather when it comes to data and function integration. Rather than using SOAP, I prefer real web services, built with HTTP.

  28. Real Web Services with REST and ICF

    This piece has become somewhat famous (or infamous) in SAP tech circles, for the approach it took and the claims it made. I'm happy to say that REST won out and that those that tried to denounce me ... failed :-)

  29. Some ramblings on URIs and identity

    Coming back from a short break from the tech world recently, I started to reacquaint myself with FOAF and RDF, amongst other things.

  30. 'Conneg' and the duality of weblogs

    Philosophy triggered by the lowly but essential connection negotiation aspect of HTTP.

  31. RSS aggregators and user-agent information for Blagg

    Tool reuse a la Unix philosophy, and more on building out the future in tiny steps.

  32. Content-Type and Blosxom's RSS

    The perils of unescaped content in feeds.

  33. For REST, read 'Architectural Style'

    In the swirling mass of memes surrounding web services it’s sometimes easy to forget that REST is an architectural style, an approach, rather than something that you install or debug.

  34. RESTifying RT

    Some notes on providing a RESTful API for Request Tracker.

  35. REST, Google, and idempotency

    Pondering the apparent conundrum of REST, Google and idempotency that Sam Ruby presented to Mark Baker.

  36. From REST to URIs, the Semantic Web, RDF, and FOAF

    Protocols and formats making up the semantic web.

  37. The 80/20 of HTTP

    Musing on how HTTP is used in the main.

  38. ETag-enabled wget

    Adding ETag awareness to the venerable wget utility.

  39. More thoughts on HTTP, Email, and Jabber

    On HTTP headers and queueing architectures.

  40. "Web^H^H^HInternet Services"? Some Ramblings.

    I’ve been pondering the term “Web Services”. While I completely understand and agree with all the reasonings behind the term (the ‘original’ services were accessible via web clients, HTTP is the underlying and ubiquitous transport, blah blah blah), I’m wondering whether “Web Services” is the best term to use.

See all tags.