BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage JSON Content on InfoQ

  • XML Can Give the Same Performance as JSON

    Many of the presumptions of how slow and resource-demanding "Fat” XML is compared to JSON’s lightweight payload do not hold up to a test David Lee, lead engineer at Marklogic, states after running a "crowd sourcing" experiment with 33 different documents and almost 1200 tests on a multitude of browsers and operating systems.

  • Don't Tell Them its REST

    Node.js has built a user-base and reputation for fast and scalable back-end systems. In a recent edition of the Nodeup podcast, four engineers share their experiences developing APIs using the platform. The conversation covers a range of key concerns including API design, security, testing, documentation, schemas and streaming. But advertising your API as RESTful may not be a good idea.

  • Twitter API v1.1 with JSON and OAuth1.0a Support

    The recently released Twitter API V1.1 ships with support for JSON and provides an ability to authenticate apps via OAuth1.0a.

  • Architectural Changes in JSON.NET 5

    Newtonsoft’s JSON.NET has received a pair of architectural updates to make it easier to use in projects that involve third party libraries. The two features are known as DefaultSettings and Extension Data.

  • Standard Java API for JSON

    JSR-353, the Java API for JSON Processing (JSON-P), has reached final approval ballot this month. JSON-P (similar to JAXP) consists of a Streaming API (similar to StAX) and an Object Model API (similar to DOM). Please note that this API does not include JSON data binding (similar to JAXB), and is unrelated to the more popular JSONP or "JSON with padding".

  • JSON Validation Roundup

    Create any “flexible” or “extensible” file format and sooner or later a group of developers will start complaining about validation. For JSON, several options are starting to spring up.

  • Getting Started with OData v3 and WCF Data Services 5.x

    If you are building new web services with .NET then OData should be high on your list of frameworks to investigate, especially if you need to support unknown third parties. The technology inherently supports both SOAP and REST style messages with the latter offering ATOM (XML) and JSON representations. This means consumers can pretty much request whatever format is best for them.

  • WCF Data Services 5.2.0 with UriParser Support

    Microsoft has announced the availability of WCF Data Services 5.2.0 with support for UriParser and fixes to several bugs.

  • Java EE 7 Expert Group Seeking Community Feedback

    As JSR 342, the specification for Java EE 7, makes its way through early draft review the expert group is keen to get community feedback on a number of open issues. These include which of the new APIs should be added to the Java EE Full/Web Profile, as well as how to better align CDI with Java EE.

  • ASP.NET Anti-Forgery Tokens With JSON Payloads

    ASP.NET MVC has AntiForgeryToken helper that allow you to detect and block CSRF attacks using user-specific tokens. However when making primarily ajax requests or using javascript frameworks such as Knockout and Backbone which have JSON payloads, the approach needs to change a bit.

  • JSONiq: The JSON Query Language

    JSONiq is a new query language that builds upon XQuery. Like SQL or LINQ, it has syntactic support concepts such as let, for, where, group by, and select.

  • Home Document Format for Non-Browser HTTP Clients

    On behalf of the IETF, Mark Nottingham has recently published a draft of the Home Documents for HTTP APIs specification. Intended for non-browser clients, it provides a way to describe resources available from a particular site as well as possible hints on how to interact with those services.

  • "The Object Network": Data Linking for Web APIs

    Developers are overwhelmed by Web APIs. APIs are being published at an alarming rate exposing a myriad ways to access data which in turn is incompatible with similar objects across other Web APIs. The Object Network is an attempt at universalizing data formats for objects to create a data fabric that leverages the network effects of hyperlinking similar to the Internet.

  • NetworkedHelpDesk's Ticket Sharing API: A Glimpse of the Future of Enterprise APIs

    Collaboration in the enterprise software space has been plagued with process and technology challenges. The advent of lightweight open API specifications from industry associations such as NetworkedHelpDesk alleviate some of these technical challenges and are being touted as examples of what future enterprise APIs will resemble.

  • Rethinking Models in MVC

    Jon Galloway is researching dynamic ASP.NET MVC 3 models using Mono’s Compiler as a Service. Meanwhile Karsten Januszewski is looking into deserialized JSON in lieu of statically typed models.

BT