Group :: Development/Ruby
RPM: gem-apipie-bindings
Navigation
Main Changelog Spec Patches Sources Download Gear Bugs and FR Repocop
Current version: 0.5.0-alt1.1
Build date: 17 february 2023, 10:27 ( 62.3 weeks ago )
Size: 29.26 Kb
Home page: https://github.com/Apipie/apipie-bindings
License: MIT
Summary: Bindings for API calls that are documented with Apipie
Description:
List of contributors List of rpms provided by this srpm:
ACL:
Build date: 17 february 2023, 10:27 ( 62.3 weeks ago )
Size: 29.26 Kb
Home page: https://github.com/Apipie/apipie-bindings
License: MIT
Summary: Bindings for API calls that are documented with Apipie
Description:
Bindings for API calls that are documented with Apipie. Bindings are generated
on the fly.
The bindings cache the apidoc from the server. It has separated caches for each
server it connects to. If the server sends the apipie checksum in the headers
Apipie-Checksum: <md5> , the bindings can expire the cache and reload updated
version before next request. If the server does not send the hashes, the cache
does not expire and has to be deleted manually when necessary.
The ability to send checksums comes with Apipie 0.1.1, see the docs on how to
set it up.
Current maintainer: Ruby Maintainers Team on the fly.
The bindings cache the apidoc from the server. It has separated caches for each
server it connects to. If the server sends the apipie checksum in the headers
Apipie-Checksum: <md5> , the bindings can expire the cache and reload updated
version before next request. If the server does not send the hashes, the cache
does not expire and has to be deleted manually when necessary.
The ability to send checksums comes with Apipie 0.1.1, see the docs on how to
set it up.
List of contributors List of rpms provided by this srpm:
- gem-apipie-bindings
- gem-apipie-bindings-doc
- gem-apipie-bindings-devel