play-ws | Standalone Play WS , an async HTTP client with fluent API | Reactive Programming library

by playframework Scala Version: 2.2.0-M2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | play-ws Summary

play-ws is a Scala library typically used in Programming Style, Reactive Programming applications. play-ws has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Play WS is a powerful HTTP Client library, originally developed by the Play team for use with Play Framework. It uses AsyncHttpClient for HTTP client functionality and has no Play dependencies. We've provided some documentation here on how to use Play WS in your app (without Play). For more information on how to use Play WS in Play, please refer to the Play documentation.

Support

Quality

Security

License

Reuse

Support

play-ws has a low active ecosystem.

It has 215 star(s) with 83 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 68 open issues and 74 have been closed. On average issues are closed in 122 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of play-ws is 2.2.0-M2

Quality

play-ws has 0 bugs and 0 code smells.

Security

play-ws has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

play-ws code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

play-ws is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

play-ws releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 7180 lines of code, 616 functions and 106 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of play-ws

Get all kandi verified functions for this library.

play-ws Key Features

No Key Features are available at this moment for play-ws.

play-ws Examples and Code Snippets

No Code Snippets are available at this moment for play-ws.

Community Discussions

Trending Discussions on play-ws

Caffeine cache in Play Framework doesn't return cached responses

QUESTION

Caffeine cache in Play Framework doesn't return cached responses

Asked 2020-Oct-02 at 00:51

I'm using Caffeine cache implementation with my java Play Framework job to cache outgoing http requests, and I see that in spite of the fact that the cache is up and running, my service still hit the external server every time instead of returning the value from the cache. And I see that the key logged in the logs is always the same.

So I see freshnessLifetime is not set, so it might mean that the cache expires immediately. but I still don't know how to set it in the config

I have not changed my java code and I cannot find any examples if I need to do that, or I'm only supposed to have a config for cache working for all outgoing requests.

I would appreciate any help with this

My build.sbt contains:

...

ANSWER

Answered 2020-Oct-02 at 00:51

I actually found how it works. The cache is not supposed to manage the lifetime like it does a separate service like Redis or Memcached but instead it acts like a browser does and is managed by the headers in HTTP response. Here: https://github.com/playframework/cachecontrol/blob/e4694aa0665e2ccc5030ae1cf1d0b15ad5b98471/src/main/scala/com/typesafe/play/cachecontrol/FreshnessCalculator.scala#L42

So the solution for me was to change the server so it serves correct header: Cache-Control "max-age=3600, public"

Source https://stackoverflow.com/questions/64161081

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install play-ws

To get started, you can add play-ahc-ws-standalone as a dependency in SBT:. Where you replace LATEST_VERSION with the version shown in this image: . This adds the standalone version of Play WS, backed by AsyncHttpClient. This library contains both the Scala and Java APIs, under play.api.libs.ws and play.libs.ws.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: