-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'github:main' into serverless
- Loading branch information
Showing
5 changed files
with
30 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
display_name: "JSON:API" | ||
created_by: Yehuda Katz, Dan Gebhardt, Gabe Sullice, Jeldrik Hanschke, Tyler Kellen, Steve Klabnik,Ethan Resnick | ||
logo: json-api.png | ||
released: May 3, 2013 | ||
short_description: "JSON:API is a specification for building APIs in JSON." | ||
topic: json-api | ||
url: https://jsonapi.org | ||
related: json, emberjs, rest-api, json-ld, hal, hateoas, siren, hydra, collection-json | ||
--- | ||
**JSON:API** is a specification for how a client should request that resources be fetched or modified, and how a server should respond to those requests. JSON:API is designed to minimize both the number of requests and the amount of data transmitted between clients and servers. This first draft was extracted from the JSON transport implicitly defined by Ember Data’s REST adapter. In general, Ember Data’s goal is to eliminate the need for ad-hoc code per application to communicate with servers that communicate in a well-defined way. The REST Adapter in Ember Data implicitly defined a protocol that custom servers could implement to get a drop-in client for all of their resources. The goals of the media type are to balance: | ||
|
||
* A generic media type that can work across a broad set of use cases, including the generally used relationship types | ||
* Similarity to existing server-side framework practices (and human readability for debugging) | ||
* Ease of implementation on the server side | ||
* Ease of implementation on the client side | ||
|
||
This specification reached a stable version 1.0 on May 29, 2015. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
--- | ||
display_name: Kokkos | ||
github_url: https://github.com/kokkos | ||
logo: kokkos.png | ||
related: c-plus-plus, parallel-computing, high-performance-computing | ||
short_description: Kokkos C++ Performance Portability EcoSystem. | ||
topic: kokkos | ||
url: https://kokkos.github.io/ | ||
--- | ||
The Kokkos C++ Performance Portability Ecosystem is a production level solution for writing modern C++ applications in a hardware agnostic way. The Ecosystem consists of multiple libraries addressing the primary concerns for developing and maintaining applications in a portable way. The three main components are the [Kokkos Core Programming Model](https://github.com/kokkos/kokkos), the [Kokkos Kernels Math Libraries ](https://github.com/kokkos/kokkos-kernels) and the [Kokkos Profiling and Debugging Tools](https://github.com/kokkos/kokkos-tools). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.