معرفی شرکت ها

تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر

تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر

تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر

تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر

تبلیغات ما

مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.

مشاهده بیشتر

توضیحات

A proxy and aggregator for querying multiple instances of an API spread across globally distributed data centers.

ویژگی	مقدار
سیستم عامل	-
نام فایل	curryproxy-2.1.1
نام	curryproxy
نسخه کتابخانه	2.1.1
نگهدارنده	[]
ایمیل نگهدارنده	[]
نویسنده	Bryan Davidson
ایمیل نویسنده	bryan.davidson@rackspace.com
آدرس صفحه اصلی	https://github.com/rackerlabs/curryproxy
آدرس اینترنتی	https://pypi.org/project/curryproxy/
مجوز	Apache 2.0

CurryProxy ========== A fast and performant proxy and aggregator for querying multiple instances of an API spread across globally distributed data centers. .. image:: https://travis-ci.org/rackerlabs/curryproxy.png :target: https://travis-ci.org/rackerlabs/curryproxy Capabilities ------------ - CurryProxy can handle multiple `routes`_ for use against different revisions of an API or for use against completely unrelated APIs. See `<etc/routes.sample.yaml>`__ for an example configuration. - Simple request forwarding (useful for preserving backwards compatability with pre-CurryProxy versions of an API hosted in a single datacenter) - Example: ``GET https://api.example.com/v1.0/foo/bar`` forwarded to ``GET https://1.api.example.com/v1.0/foo/bar`` - Advanced request forwarding to multiple endpoints - Example: ``GET https://api.example.com/1,2/v1.0/foo/bar`` forwarded to the following: - ``GET https://1.api.example.com/v1.0/foo/bar`` - ``GET https://2.api.example.com/v1.0/foo/bar`` - Requests are made in parallel - JSON responses received from multiple endpoints are `aggregated`_ and returned to the client - Example: ``{"foo": 1}`` received from 1 and ``{"bar": 2}`` received from 2 are aggregated to ``[{"foo": 1}, {"bar": 2}]`` and returned to the client - Rich, meaningful `errors`_ logged and returned to the client when a proxied request fails .. _`routes`: https://github.com/rackerlabs/curryproxy/wiki/Routes .. _`aggregated`: https://github.com/rackerlabs/curryproxy/wiki/Multiple-Endpoints-Aggregation .. _`errors`: https://github.com/rackerlabs/curryproxy/wiki/Multiple-Endpoints-Aggregation#error-handling Installation ------------ ``pip install curryproxy`` will do what you expect. There are a couple of extra options: - ``pip install curryproxy[tests]``. This will install any packages required to run the tests. - ``pip install curryproxy[frozen]``. This will install curryproxy with explicitly pinned dependencies, as generated by ``pip freeze``. This is intended as a convenience for those who want the package to provide a reproducible environment. The versions used will be the latest working ones at the time the given Curry version was released. You will need to provide `configuration files`_ before starting Curry. .. _`configuration files`: etc/ **NOTE**: The configuration files have changed in v2.x. ``routes.json`` and ``logging.conf`` have become ``routes.yaml`` and ``logging.yaml`` respectively. See the sample files for examples. Limitations ----------- - Merging responses from multiple endpoints together occurs only under certain conditions outlined on the `Multiple Endpoints Aggregation`_ wiki page. .. _`Multiple Endpoints Aggregation`: https://github.com/rackerlabs/curryproxy/wiki/Multiple-Endpoints-Aggregation Testing ------- Tests are set up to run with ``tox``. The default ``tox`` setup creates environments for each known-usable version of each of our dependencies, and runs the tests in each of them. That amounts to around a dozen environments at the moment, so you'll probably want to run them in parallel with ``tox -p auto``. If you don't want to be that thorough (perhaps you're smoke testing a work in progress), you can run against only the most recent supported versions of dependencies with ``tox -e py36``. You can test against specific dependency versions like this: :: tox -e py36-requests2.{2,3,4,5,6,7} -p auto tox -e py36-webob1.{2,3,4,5} -p auto tox -e py36-grequests0.{2,3} -p auto tox -e py36-requests.latest ``tox -e lint`` is also available, and will run various linting checks. Roadmap ------- - OData support for server-side ordering and paging - Response caching for a specified time

نیازمندی

مقدار	نام
<0.4,>=0.3	grequests
<4,>=3.10	pyyaml
<2.8,>=2.2	requests
<1.5,>=1.2	webob
==1.4.2	WebOb
==1.4.0	gevent
==0.4.15	greenlet
==0.3.0	grequests
==3.13	pyyaml
==2.7.0	requests
-	mock
-	testtools

زبان مورد نیاز

مقدار	نام
>=3	Python

نحوه نصب

نصب پکیج whl curryproxy-2.1.1:

pip install curryproxy-2.1.1.whl

نصب پکیج tar.gz curryproxy-2.1.1:

pip install curryproxy-2.1.1.tar.gz