DPP clients есть практически на все: ( http://meteorpedia.com/read/DDP_Clients ). Плюс ко всему в метеоре есть понятие Optimistic UI которое базируется на интеграции данных с помощью DDP, LiveQuery, and Minimongо и выпилвания DDP вместе с фичами subscribe and publish создает из Метеора хромую лошадь. ( http://info.meteor.com/blog/optimistic-ui-with-meteor-latency-compensation ).
Из вашего введения как-то не совсем ясно зачем создавать RESTful сервис на метор для комуникации клиента и сервера. Meteor имеет всроенный bidirectional DDP connection, что позволяет пересылать данные более эффективно. Более того, официальная документация довольно подробно открывает тему REST в Метеор (http://meteorpedia.com/read/REST_API). Вкратце:
" it's critical to understand that if you are making an API for your own apps and tools, you've got it wrong! We hope it's very clear that between the server and client, you have a bidirectional DDP connection that handles realtime syncing of published data (see Publish and Subscribe in the docs).
Beyond that, if you're building an external tool that requires live data and will manipulate this data, the correct way to do this is with a DDP Client. This will save you a lot of wasted time and effort in writing completely unnecessary code."
" it's critical to understand that if you are making an API for your own apps and tools, you've got it wrong! We hope it's very clear that between the server and client, you have a bidirectional DDP connection that handles realtime syncing of published data (see Publish and Subscribe in the docs).
Beyond that, if you're building an external tool that requires live data and will manipulate this data, the correct way to do this is with a DDP Client. This will save you a lot of wasted time and effort in writing completely unnecessary code."