blocks|key|1150505|text|不，安卓没有REST+API，你可以实现你自己的，因为它支持Apache+HTTP客户端和JavaSE+HttpURLConnection。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1150506|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

No, there is no REST API in Android, you can implement your own as it support Apache HTTP Client and JavaSE HttpURLConnection.

blocks|key|3413571|text|我刚刚在伦敦DroidCon+2012大会上参加了一个关于RoboSpice的演讲。它似乎可以为您处理任何网络任务。此外，REST是内置支持的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3413572|点击这里查看：https://github.com/octo-online/robospice|offset|length|3413573|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/octo-online/robospice^0|0|7|14|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I just attended a presentation about RoboSpice at DroidCon 2012 London. It seems it can handle any networking task for you. Also, REST is built-in supported.

Check it out here: <a href="https://github.com/octo-online/robospice" rel="nofollow">https://github.com/octo-online/robospice</a>

blocks|key|1097654|text|不存在这样的通用REST服务引擎。您可以使用DownloadManager来获取某些远程资源，然后检查它何时被接收，然后自己处理它，但是没有提供通用数据处理和显示的模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1097655|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/reference/android/app/DownloadManager.html^0|M|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

No such general purpose REST service engine exists. You could use <a href="http://developer.android.com/reference/android/app/DownloadManager.html" rel="nofollow">DownloadManager</a> to fetch certain remote resources and then check to see when it is received and then process it yourself but there is nothing that provides the pattern of generic data processing and display.

blocks|key|3413537|text|Novoda+RESTProvider看起来很有前途。我还没有试过，但它似乎已经覆盖了一些部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3413538|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/novoda/RESTProvider^0|0|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="https://github.com/novoda/RESTProvider" rel="nofollow">Novoda RESTProvider</a> looks promising. I haven't tried it yet, but it seems to have some parts covered.

blocks|key|4882554|text|有一种我过去用过的方法。这些的奇妙之处在于它是非常灵活的。它基于在executor中创建、设置和排队的请求(可运行的或可调用的)(因此，是的，您可以控制并发线程的数量和执行请求的方式，甚至可以对它们进行优先排序)。另一件很棒的事情是，你可以决定如何处理这些响应。我强烈建议在后台对UI或用户透明地进行解析(即:直接写入数据库、SharedPreferences等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4882555|最后一件很棒的事情是，当请求完成时，您能够获得响应，以防您需要进行一些更新或向用户显示一些信息。这可以通过设置一个随请求一起执行的回调来轻松完成。另一种选择是使用Google+Guava+ListenableFuture作为回调。|4882556|这里有一个关于整个系统的更深入的解释：http://joseluisugia.wordpress.com/2012/07/02/theres-life-after-asynctasks-in-android/|offset|length|4882557|这里有一个非常基本的工作示例，并附上了源代码：http://joseluisugia.wordpress.com/2012/08/03/using-runnables-queues-and-executors-to-perform-tasks-in-background-threads-in-android/|4882558|希望能有所帮助。回答继续讨论。|4882559|entityMap|0|LINK|mutability|MUTABLE|url|http://joseluisugia.wordpress.com/2012/07/02/theres-life-after-asynctasks-in-android/|1|http://joseluisugia.wordpress.com/2012/08/03/using-runnables-queues-and-executors-to-perform-tasks-in-background-threads-in-android/^0|0|0|J|2D|0|0|N|3O|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

There is one approach I've used in the past. The fantastic thing about these is that it is really flexible.
It is based in requests (Runnable or Callables) which are created, setted up and enqueued within an executor (so yes, you can control the number of concurrent threads and the way requests are executed, you can even prioritize them). 
One another great thing is that you can decide what to do with the responses. I'd strongly recommend to parse to do this in the background transparently to the UI or the user (ie.: Writing directly into database, SharedPreferences, etc). 

The last great thing is that you are able to get the response back when the request is finished in case you need to make some updates or present some info to the user. This can be easily done by setting up a callback which goes along with the request. Another option would be using Google Guava ListenableFuture as a callback.

There's a more in-depth explanation about the whole system here:
<a href="http://joseluisugia.wordpress.com/2012/07/02/theres-life-after-asynctasks-in-android/" rel="nofollow">http://joseluisugia.wordpress.com/2012/07/02/theres-life-after-asynctasks-in-android/</a>

And a very basic working example here with source code attached:
<a href="http://joseluisugia.wordpress.com/2012/08/03/using-runnables-queues-and-executors-to-perform-tasks-in-background-threads-in-android/" rel="nofollow">http://joseluisugia.wordpress.com/2012/08/03/using-runnables-queues-and-executors-to-perform-tasks-in-background-threads-in-android/</a>

Hope it helps.
Answer back to keep on the discussion.

blocks|key|1144890|text|我谨慎地推荐Spring+Android+Rest客户端。JSON/XML是一个很棒的api+...des/序列化和连接模板，非常容易使用。有关详细信息，请参阅http://static.springsource.org/spring-android/docs/1.0.x/reference/html/rest-template.html。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1144891|entityMap|0|LINK|mutability|MUTABLE|url|http://static.springsource.org/spring-android/docs/1.0.x/reference/html/rest-template.html^0|28|2I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I suggest carefully the Spring Android Rest Client. Its a beautiful api with JSON/XML... des/serializers and Connection Template, very easy to use. See <a href="http://static.springsource.org/spring-android/docs/1.0.x/reference/html/rest-template.html" rel="nofollow">http://static.springsource.org/spring-android/docs/1.0.x/reference/html/rest-template.html</a> for more information.

Is there any kind of rest engine service.

In general having REST web service and android app that will fetch from it and make some data processing and have it displayed is something that fits to common pattern.

It would be natural to have service that could be queried over content provider or similar and retrieve data. Service would have some kind of definitions of data that it will fetch.

Anyone knows of something like that?

Android Rest Service Engine

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

是否有任何类型的rest引擎服务。一般来说，拥有REST web服务和android应用程序，可以从其中获取数据并进行一些数据处理和显示，这符合常见的模式。可以通过内容提供商或类似服务查询并检索数据服务是很自然的。服务将具有它将获取的数据的某种类型的定义。有人知道这样的事情吗？

问Android Rest服务引擎
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android Rest服务引擎EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android Rest服务引擎
EN