blocks|key|1755792|text|我想您可能可以使用Meteor创建一个RESTful服务，但这并不是框架的真正目的--+Meteor的主要优点之一是客户端和服务器之间的紧密交互，而web服务没有客户端。如果你喜欢node.js，我建议你考虑用Ruby语言编写一个web服务后端，或者像https://github.com/intridea/grape这样的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1755793|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/intridea/grape^0|3I|X|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 suppose you probably could create a RESTful service using Meteor, but it's not really what the framework is intended for -- one of the main benefits of Meteor is tight interaction between the client and the server, and a web service doesn't have a client side. I'd recommend looking into either writing a web service back end in node.js on its own or something like <a href="https://github.com/intridea/grape" rel="nofollow">https://github.com/intridea/grape</a> if you like Ruby.

blocks|key|1756064|text|我在气象百科上写了一篇完整的文章：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1756065|http://www.meteorpedia.com/read/REST_API|offset|length|1756066|这篇文章回顾了创建REST接口的所有6个选项，从最高级别(例如，为您处理一切的智能包)到最低级别(例如，编写您自己的connectHandler)。|1756067|此外，这篇文章还涵盖了在Meteor中使用REST接口是正确还是错误的问题，参考了Meteor+REST测试工具，并解释了常见的陷阱，如CORS安全问题。|1756068|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|14|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]]]

I did a full write-on on this in Meteorpedia:

<a href="http://www.meteorpedia.com/read/REST_API">http://www.meteorpedia.com/read/REST_API</a>

The post reviews all 6 options for creating REST interfaces, from highest level (e.g. smart packages that handle everything for you) to lowest level (e.g. writing your own connectHandler).

Additionally the post covers when using a REST interface is the right or wrong thing to do in Meteor, references Meteor REST testing tools, and explains common pitfalls like CORS security issues.

blocks|key|1755838|text|我最初回答了这个问题here，但重述一下：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1755839|要在您的数据之上添加RESTful方法，请查看为Meteor编写的Collection+API：|1755840|https://github.com/crazytoad/meteor-collectionapi|1755841|至于访问数据库的身份验证，请看下面的项目：|1755842|https://github.com/meteor/meteor/wiki/Getting-started-with-Auth|1755843|两者都还处于开发阶段，但您可以创建一个RESTful应用程序接口，并很容易地将其与移动本地客户端集成。|1755844|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/11167874|1|2^0|A|4|0|0|0|0|1D|1|0|0|0|1R|2|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|L|3|M|5|6|7|1B|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|G]]|W|$5|Q|R|S|C|$T|K]]]]

I originally answered this question <a href="https://stackoverflow.com/a/11167874">here</a>, but to recap:

For adding RESTful methods on top of your data, look into the Collection API written for Meteor:

<a href="https://github.com/crazytoad/meteor-collectionapi" rel="nofollow noreferrer">https://github.com/crazytoad/meteor-collectionapi</a>

As for authentication for accessing the database, take a look at this project:

<a href="https://github.com/meteor/meteor/wiki/Getting-started-with-Auth" rel="nofollow noreferrer">https://github.com/meteor/meteor/wiki/Getting-started-with-Auth</a>

Both are definitely infantile in development, but you can create a RESTful API and integrate it with a mobile native client pretty easily.

blocks|key|2125780|text|我知道这是一个古老的线程，但为了防止有人偶然发现它，我发布了一个用Meteor+0.9.0%2B编写REST+API的包：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2125781|https://github.com/kahmali/meteor-restivus|offset|length|2125782|它是受RestStop2的启发，使用Iron+Router的服务器端路由构建的，在我看来，这是一个比这里发布的任何东西都更好的解决方案。|2125783|更新：为了澄清为什么我认为这是一个比上面提到的更好的解决方案，我只想指出它们之间的区别：|style|BOLD|2125784|CollectionAPI:|2125785|CollectionAPI仅限于在集合上公开非常基本的CRUD操作。我在移动应用程序中使用REST+API，对于我来说，发送整个文档可能非常浪费，而且大多数时候我需要执行一些额外的数据处理(例如，在REST端点中发送Google+Cloud消息以添加朋友，但只有在成功添加朋友的情况下)。CollectionAPI为您提供了一个在端点执行之前运行的钩子，但据我所知，在响应之前没有任何内容，因此您无法修改返回的数据。对于身份验证，CollectionAPI允许您定义必须随每个请求一起传递的authToken。这更像是一个传统的api密钥，因为它似乎是硬编码到您的应用程序中的，因此对每个用户都是相同的。|2125786|Restivus，因为它不限于自动化的收集工作，使您能够完全控制您的端点。它现在提供了Collection+API中包含的所有功能。它还支持用户身份验证和角色权限，因此您可以识别发出请求的用户(并从经过身份验证的端点中轻松访问该用户)。它还提供了登录和注销端点来帮助实现这一点。我将在最后提供一个Restivus的代码示例。|2125787|HTTP.publish:|2125788|据我所知，这与CollectionAPI类似，因为它仅限于公开集合上的基本CRUD操作。这个函数更明确地绑定到Meteor的发布，并允许您使用publish函数来处理GET请求。我对文档感到困惑，但它可能有也可能没有一些基本的身份验证可用。我以前没有用过它，但我不是它的API的狂热粉丝，它感觉有点笨拙。一旦我发表了更广泛的文章，我会尝试重新访问它。同一团队有另一个名为HTTP.methods的包，它不提供对发布功能的访问，但具有类似于Restivus的api，并且在当时具有类似的功能。|2125789|Restivus是“更好的”，因为它不会限制您使用自己的发布函数，因此允许对端点进行更细粒度的控制。如果您只是希望将发布函数公开给外部应用程序接口，我建议您坚持使用HTTP.publish。Restivus还有一个更简单的API，并支持HTTP+PATCH方法(似乎没有其他包承认它的存在)。他们的HTTP.methods包与Restivus非常相似，除了它缺乏补丁支持，尽管它提供了一些基本的身份验证，但我相信您只能对所有端点进行身份验证，或者不进行身份验证。Restivus将允许您在每个端点(而不仅仅是每个路由)级别上进行控制。端点上的角色权限(例如，用户、管理员)在Restivus上也是可用的，但我在HTTP.methods上看不到任何关于这方面的内容。|2125790|流星路由器：|2125791|为了支持Iron+Router，此选项已被弃用，请参阅下面的内容。|2125792|铁质路由器：|2125793|Iron+Router非常棒，但它并不是专门为构建REST+API而设计的。最近他们添加了对应于HTTP方法(GET、POST等)的函数，但它们不支持任何形式的身份验证，而且您只能访问较低级别的Node+request和response对象，因此您将被迫学习如何使用这些对象。一旦你这样做了，你会发现在每个端点中都有一些重复的工作要做，比如用正确的头和响应代码创建响应。如果您的API是从浏览器使用的，您还必须担心CORS遵从性。|2125794|Restivus实际上构建在Iron+Router之上，并在端点上提供身份验证层。它还抽象了与Node请求和响应对象直接交互的需要，尽管它们仍然存在，以防我们遗漏了任何东西。因此，它通过更高级别的API利用了Iron+Router的所有强大之处，为您提供了编写代码的乐趣。如果你已经在使用Iron+Router，Restivus是很棒的，因为它不会增加任何额外的依赖。|2125795|RestStop2:|2125796|实际上，我在一个正在开发的项目中使用RestStop2时，它被弃用，取而代之的是Iron+Router。他们有扎实的文档，还有一个我最喜欢的API。根据他们的建议，我在Iron+Router上构建了一个新的软件包，这个软件包非常受RestStop2的启发。Restivus现在在RestStop2+GitHub页面上得到了认可，所以我认为他们同意它是一个值得替代的产品。|2125797|下面是来自Restivus文档的快速入门部分的一小段代码：|2125798|if(Meteor.isServer)+{
++Meteor.startup(function+()+{
++++//+Global+configuration
++++Restivus.configure({
++++++useAuth:+true,
++++++prettyJson:+true
++++});

++++//+Generates:+GET,+POST+on+/api/users+and+GET,+DELETE+/api/users/:id+for
++++//+Meteor.users+collection
++++Restivus.addCollection(Meteor.users,+{
++++++excludedEndpoints:+['deleteAll',+'put'],
++++++routeOptions:+{
++++++++authRequired:+true
++++++},
++++++endpoints:+{
++++++++post:+{
++++++++++authRequired:+false
++++++++},
++++++++delete:+{
++++++++++roleRequired:+'admin'
++++++++}
++++++}
++++});

++++//+Maps+to:+POST+/api/articles/:id
++++Restivus.addRoute('articles/:id',+{authRequired:+true},+{
++++++post:+{
++++++++roleRequired:+['author',+'admin'],
++++++++action:+function+()+{
++++++++++var+article+=+Articles.findOne(this.urlParams.id);
++++++++++if+(article)+{
++++++++++++return+{status:+"success",+data:+article};
++++++++++}
++++++++++return+{
++++++++++++statusCode:+400,
++++++++++++body:+{status:+"fail",+message:+"Unable+to+add+article"}
++++++++++};
++++++++}
++++++}
++++});
++});
}|code-block|syntax|javascript|2125799|entityMap|0|LINK|mutability|MUTABLE|url|1|http://github.differential.com/reststop2/|2|https://github.com/EventedMind/iron-router^0|0|0|16|0|0|3|9|1|I|B|2|0|0|3|0|0|E|0|0|0|0|D|0|0|0|0|6|0|0|0|6|0|0|0|0|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1U|8|@]|9|@$D|1V|E|1W|1|1X]]|A|$]]|$1|F|3|G|5|6|7|1Y|8|@]|9|@$D|1Z|E|20|1|21]|$D|22|E|23|1|24]]|A|$]]|$1|H|3|I|5|6|7|25|8|@$D|26|E|27|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|28|8|@$D|29|E|2A|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|2B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2C|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|2D|8|@$D|2E|E|2F|J|K]]|9|@]|A|$]]|$1|T|3|U|5|6|7|2G|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2H|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2I|8|@$D|2J|E|2K|J|K]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2L|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2M|8|@$D|2N|E|2O|J|K]]|9|@]|A|$]]|$1|13|3|14|5|6|7|2P|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|2R|8|@$D|2S|E|2T|J|K]]|9|@]|A|$]]|$1|19|3|1A|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|2V|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|1F|7|2W|8|@]|9|@]|A|$1G|1H]]|$1|1I|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]]|1J|$1K|$5|1L|1M|1N|A|$1O|C]]|1P|$5|1L|1M|1N|A|$1O|1Q]]|1R|$5|1L|1M|1N|A|$1O|1S]]]]

I know this is an old thread, but in case anyone stumbles across it, I published a package for writing REST APIs in Meteor 0.9.0+:

<a href="https://github.com/kahmali/meteor-restivus">https://github.com/kahmali/meteor-restivus</a>

It was inspired by <a href="http://github.differential.com/reststop2/">RestStop2</a> and built with <a href="https://github.com/EventedMind/iron-router">Iron Router</a>'s server-side routing. In my not-so-humble opinion, it's a better solution than anything posted here thus far.

UPDATE: To clarify why I think it's a "better" solution than those mentioned, I'll just point out the differences between each:

CollectionAPI: 
CollectionAPI is limited to exposing very basic CRUD operations on your collections. For my use, which is consuming the REST API in mobile apps, it can be extremely wasteful to send down entire documents, and most of the time I need to do some additional processing of data (for instance, sending a Google Cloud Message in a REST endpoint for adding a friend, but only if the friend is successfully added). CollectionAPI gives you a hook that runs before the endpoint is executed, but from what I understand there is nothing immediately before the response, so you have no way of modifying the data that is returned. For authentication, CollectionAPI allows you to define an authToken that must be passed with each request. This acts more like a traditional api key, as it appears to be hard-coded into your app, and would therefore be the same for every user. 

Restivus, since it is not limited to automated work on collections, gives you complete control over your endpoints. It now provides all the functionality included in Collection API. It supports user authentication and role permissions as well, so you can identify the user making the request (and easily access that user from within authenticated endpoints). It provides a login and logout endpoint as well to assist with that. I will provide a code example for Restivus at the end. 

HTTP.publish: 
From what I understand, this is similar to CollectionAPI in that it is limited to exposing basic CRUD operations on collections. This one is more specifically tied to Meteor's publishing, and allows you use a publish function for handling GET requests. I'm confused by the documentation, but it may or may not have some basic authentication available. I haven't used this before, but I'm not a big fan of the API for it, which feels a bit clunky. Once I'm publishing more extensively I'll try to revisit it. The same team has another package called HTTP.methods which doesn't give you the access to the publish functions, but has a similar api to Restivus and, at the time, similar functionality. 

Restivus is "better" because it doesn't limit you to using your publish functions, and therefore allows for a much finer-grained control over your endpoints. If you are just looking to expose your publish functions to an external API, I would recommend you stick with HTTP.publish. Restivus also has a simpler API and supports the HTTP PATCH method (which no other package seems to acknowledge exists). Their HTTP.methods package is pretty similar to Restivus, except it lacks PATCH support, and although it offers some basic authentication, I believe you only have the ability to make all endpoints authenticated, or none. Restivus will allow you to control that on a per-endpoint (not just per-route) level. Role permissions (e.g., user, admin) on endpoints are also available on Restivus, but I don't see anything about that for HTTP.methods.

Meteor Router: 
This has been deprecated in favor of Iron Router, please see below.

Iron Router: 
Iron Router is awesome, but it is not specifically designed for building REST APIs. Recently they added functions corresponding to the HTTP methods (GET, POST, etc.), but they don't support any form of authentication, and all you have access to is the lower-level Node request and response objects, so you'll be forced to learn how to work with those. Once you do, you'll find that there is some repetitive work to be done in each endpoint, like creating responses with the proper headers and response codes. You'll also have to worry about CORS compliance if your API is being consumed from the browser. 

Restivus is actually built on top of Iron Router, and provides a layer of authentication on endpoints. It also abstracts away the need for direct interaction with the Node request and response objects, although they're still there in case we've missed anything. So it's using all the awesomeness of Iron Router with a higher-level API for your coding pleasure. Restivus is great if you're already using Iron Router, since it won't add any additional dependency. 

RestStop2: 
I was actually using RestStop2 in a project I'm working on when it was deprecated in favor of Iron Router. They had solid documentation, and an API I preferred above the others. Per their suggestion, I built a new package on top of Iron Router, which is very much inspired by RestStop2. Restivus is now being endorsed on the RestStop2 GitHub page, so I think they agree that it's a worthy replacement. 

Here's a little code snippet from the Quick Start section of the Restivus docs: 

<pre><code>if(Meteor.isServer) {
 Meteor.startup(function () {
 // Global configuration
 Restivus.configure({
 useAuth: true,
 prettyJson: true
 });

 // Generates: GET, POST on /api/users and GET, DELETE /api/users/:id for
 // Meteor.users collection
 Restivus.addCollection(Meteor.users, {
 excludedEndpoints: ['deleteAll', 'put'],
 routeOptions: {
 authRequired: true
 },
 endpoints: {
 post: {
 authRequired: false
 },
 delete: {
 roleRequired: 'admin'
 }
 }
 });

 // Maps to: POST /api/articles/:id
 Restivus.addRoute('articles/:id', {authRequired: true}, {
 post: {
 roleRequired: ['author', 'admin'],
 action: function () {
 var article = Articles.findOne(this.urlParams.id);
 if (article) {
 return {status: "success", data: article};
 }
 return {
 statusCode: 400,
 body: {status: "fail", message: "Unable to add article"}
 };
 }
 }
 });
 });
}
</code></pre>

blocks|key|111383|text|现在，任何人偶然发现这一点(2013%2B)，请查看Meteor+Router+smart包，它为server+side+routing提供了在创建RESTful界面时有用的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|111384|Meteor.Router.add('/404',+[404,+"There's+nothing+here!"]);|code-block|syntax|javascript|111385|为了在以后的搜索中为您提供帮助，请务必查看https://atmosphere.meteor.com+--一个智能软件包存储库。对于版本和包管理，Meteorite是一个非常方便的CLI工具。|111386|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/tmeasday/meteor-router|1|https://github.com/tmeasday/meteor-router#server-side-routing|2|https://atmosphere.meteor.com/|3|http://oortcloud.github.io/meteorite/^0|O|D|0|1B|J|1|0|0|L|T|2|21|9|3|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]|$A|1A|B|1B|1|1C]]|C|$]]|$1|K|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]|U|$5|N|O|P|C|$Q|V]]|W|$5|N|O|P|C|$Q|X]]]]

Anyone stumbling across this now (2013+), checkout the <a href="https://github.com/tmeasday/meteor-router">Meteor Router</a> smart package, which provides methods for <a href="https://github.com/tmeasday/meteor-router#server-side-routing">server side routing</a> useful in creating RESTful interfaces.

<pre><code>Meteor.Router.add('/404', [404, "There's nothing here!"]);
</code></pre>

To assist you in future searches, be sure to take a look at <a href="https://atmosphere.meteor.com">https://atmosphere.meteor.com</a> - a smart package repository. And <a href="http://oortcloud.github.io/meteorite/">Meteorite</a> is a pretty handy CLI tool for version and package management.

blocks|key|1756026|text|最优雅的解决方案似乎是HTTP.publish。它并没有像其他人那样发明一个新的publish，而是简单地将HTTP协议添加到现有的Meteor接口中。这意味着，例如，Meteor.allow和Meteor.deny可以自动为HTTP和DDP工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1756027|示例：|1756028|如果提供了一个集合和一个发布函数，则HTTP.publish将挂载到以下URL和方法上：|1756029|GET+-+/api/list+-所有已发布数据|1756030|POST+-+/api/list+-将文档插入到集合中|1756031|GET+-+/api/list/:id+-查找一个已发布的文档|1756032|PUT+-+/api/list/:id+-更新文档|1756033|DELETE+-+/api/list/:id+-删除文档|1756034|1756035|myCollection+=+new+Meteor.Collection('list');

//+Add+access+points+for+`GET`,+`POST`,+`PUT`,+`DELETE`
HTTP.publish(myCollection,+function(data)+{
++//+this.userId,+this.query,+this.params
++return+myCollection.find({});
});|code-block|syntax|javascript|1756036|它做了not+yet+handle+authentication+completely。|1756037|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/CollectionFS/Meteor-http-publish|1|http://docs.meteor.com/#meteor_publish|2|https://github.com/CollectionFS/Meteor-http-methods#login-and-logout-todo^0|14|7|2C|C|2P|B|B|C|0|14|7|1|0|0|I|C|0|0|0|0|0|0|0|0|3|14|2|0^^$0|@$1|2|3|4|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@$9|1K|A|1L|1|1M]|$9|1N|A|1O|1|1P]]|E|$]]|$1|F|3|G|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1U|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1V|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1W|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1X|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|20|8|@]|D|@]|E|$X|Y]]|$1|Z|3|10|5|6|7|21|8|@]|D|@$9|22|A|23|1|24]]|E|$]]|$1|11|3|-4|5|6|7|25|8|@]|D|@]|E|$]]]|12|$13|$5|14|15|16|E|$17|18]]|19|$5|14|15|16|E|$17|1A]]|1B|$5|14|15|16|E|$17|1C]]]]

The most elegant solution appears to be <a href="https://github.com/CollectionFS/Meteor-http-publish" rel="nofollow noreferrer">HTTP.publish</a>. Rather than invent a new API like the others, it simply adds the HTTP protocol to the existing Meteor <a href="http://docs.meteor.com/#meteor_publish" rel="nofollow noreferrer"><code>publish</code></a> interface. This means, for example, that <code>Meteor.allow</code> and <code>Meteor.deny</code> work automatically for HTTP as well as DDP.
Example:
<blockquote>
If handed a collection and a publish function the <code>HTTP.publish</code> will mount on the following URLs and methods:
GET - /api/list - all published data 
POST - /api/list - insert a document into collection 
GET - /api/list/:id - find one published document 
PUT - /api/list/:id - update a document 
DELETE - /api/list/:id - remove a document
</blockquote>
<pre><code>myCollection = new Meteor.Collection('list');

// Add access points for `GET`, `POST`, `PUT`, `DELETE`
HTTP.publish(myCollection, function(data) {
 // this.userId, this.query, this.params
 return myCollection.find({});
});
</code></pre>
It does <a href="https://github.com/CollectionFS/Meteor-http-methods#login-and-logout-todo" rel="nofollow noreferrer">not yet handle authentication completely</a>.

blocks|key|2130529|text|可以，您可以使用私有API向Meteor公开REST端点。该功能将很快公开，但在此期间，请参阅Can+I+mount+another+route+handler+through+____meteor_bootstrap____.app?。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2130530|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/10119777/can-i-mount-another-route-handler-through-meteor-bootstrap-app^0|1B|1Z|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]]]]

Yes, you can expose REST endpoints with Meteor using the private API. The functionality will become public soon, but in the meantime, see <a href="https://stackoverflow.com/questions/10119777/can-i-mount-another-route-handler-through-meteor-bootstrap-app">Can I mount another route handler through ____meteor_bootstrap____.app?</a>.

blocks|key|111574|text|我知道这是一个古老的话题，但您可以使用Meteor+WebApp包：https://docs.meteor.com/packages/webapp.html，而不是使用任何外部包。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|111575|希望它能帮上忙！|111576|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.meteor.com/packages/webapp.html^0|Y|18|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I know this is an old topic, but instead of using any external package, you can use the Meteor WebApp package: 
<a href="https://docs.meteor.com/packages/webapp.html" rel="nofollow noreferrer">https://docs.meteor.com/packages/webapp.html</a>.

Hope it helps!

blocks|key|111424|text|我想我应该更新2014年的对话。我还没有找到在Meteor中实现REST服务的完美方法，我希望有人能给我指出另一个研究方向。我测试了3个项目，每个项目都有自己的缺点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|111425|我使用过meteor-router，但github的页面上说，它只会在未来修复错误，并在所有新项目中使用Iron+Router。我仍然在考虑使用它，因为如果它适用于我，那么除了某种类型的身份验证之外，升级是不必要的。|111426|我有一个使用Iron+Router构建的简单示例服务，但它似乎比meteor-router支持更少的REST服务，并且如果有人将无效的json发布到rest端点，就会导致服务器崩溃。|111427|为基本CRUD操作提供了REST+api支持，但它似乎不支持按id以外的查询。|111428|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I thought I would update the conversation for 2014. I still haven’t found the perfect way to implement REST services in Meteor and I’m hoping someone can point me in another direction to investigate. I’ve tested 3 projects and each have their drawbacks:

<a href="https://github.com/tmeasday/meteor-router" rel="nofollow">meteor-router</a>
I worked with meteor-router but the github page says it will only be fixing bugs going forward and to use Iron Router on all new projects. I’m still considering using this since if it works for me as-is then upgrades aren’t necessary except for some type of authentication.

<a href="https://github.com/EventedMind/iron-router" rel="nofollow">iron-router</a> 
I have a simple example service built using Iron Router but it appears to support REST services even less than meteor-router and causes the server to crash if someone posts invalid json to rest endpoint. 

<a href="https://github.com/crazytoad/meteor-collectionapi" rel="nofollow">meteor-collectionapi</a> 
Exposes a REST api for basic CRUD operations are support but it doesn’t appear to support queries other than by id.

How would you go about creating a restful web service using Meteor. I would like to create apps in Appcelerator that hook into the same backend.

Can Meteor solve this problem?

How to expose a RESTful Web Service using Meteor

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如何使用Meteor创建restful风格的web服务？我想在Appcelerator中创建应用程序，挂钩到相同的后端。Meteor能解决这个问题吗？

问如何使用Meteor公开RESTful网络服务
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Meteor公开RESTful网络服务EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Meteor公开RESTful网络服务
EN