Comments (2)
I was wondering the same thing
from robozombie.
The goals are pretty much the same for both projects, but there's a difference in the way you use some of the features.
For example, converters are segregated into serializers and deserializers and multiple types can be hierarchically defined on the endpoint interface itself. Interceptors can read the metadata for the invocation context, so for example you could process the request based on your custom annotations.
Interceptors can be passed as arguments to the request methods and they hook you into the very end of the request-processor chain. So you pretty much have the final say by scrutinizing the whole chain, altering the request using info at the point of invocation or aborting it if you wish.
A few others are: a uniform API for both request and response headers, support for passing multivalued query and form-urlencoded parameters in a Map
and explicit support for 8 HTTP method types and Apache HC's entity types. Some differences in the contracts for asynchronous invocation and error handling ...etc.
The current release (1.3.3) does not offer multipart requests and there's no support for RxJava.
from robozombie.
Related Issues (20)
- Streamline response handling by delegating to a chain of processors HOT 1
- Add support for HTTP PATCH requests
- Deprecate constructor injection for endpoints
- Eliminate coupling with GSON and Simple-XML
- Allow batch identification of query and form params
- Separate content conversion to serialization and deserialization
- Update request metadata to be more concise and expressive
- Allow inherited metadata to be detached from a request definition
- Support interception of requests prior to execution
- Unify all request failures under a single context aware exception
- Consolidate parameters for @Endpoint
- Enable selective component skipping
- Confine hierarchical searches for wired endpoints
- Fix TypeToken usage on JsonDeserializer
- RoboZombie with ProGuard HOT 1
- Allow explicit identification of query params, form-url-encoded params and entities to be enclosed
- Eliminate the need for a separate annotation on RESTful requests
- Streamline request handling by delegating to a chain of processors
- Allow separate request execution configurations to be tailored for each endpoint
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from robozombie.