[
https://issues.apache.org/jira/browse/COUCHDB-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johnny Weng Luu updated COUCHDB-1219:
-------------------------------------
Description:
With CouchDB the application server landscape has changed. The database can now
handle almost all logic that is data related, eg. validation, updating,
formatting etc.
It has a HTTP server for incoming requests but one thing I find missing is a
HTTP client that can push data to other servers.
What I have to do right now for sending data to an external service is to setup
a (node.js) server that listens on the _changes feed.
When there is a document meant for being delivered through email, node.js will
send a HTTP request to the (sendgrid) email service.
I think it would make sense if CouchDB could make HTTP requests on document
changes, meaning we can eliminate that extra HTTP client layer just for sending
the data.
Why only have a HTTP server for data but not a HTTP client for data.
I think this would make CouchDB even more suitable for couchapps.
Now the app can be offline. We send an email and it will be sent by couchdb
when Internet connectivity is there.
Also now the whole app can be replicated and every couchdb instance can make
it's own HTTP requests and we no longer have to have a node.js server just to
support basic HTTP requests.
was:
With CouchDB the application server landscape has changed. The database can now
handle almost all logic that is data related, eg. validation, updating,
formatting etc.
It has a HTTP server for incoming requests but one thing I find missing is a
HTTP client that can push data to other servers.
What I have to do right now for sending data to an external service is to setup
a (node.js) server that listens on the _changes feed.
When there is a document meant for being delivered through email, node.js will
send a HTTP request to the (sendgrid) email service.
I think it would make sense if CouchDB could make HTTP requests on document
changes, meaning we can eliminate that extra HTTP client layer just for sending
the data.
Why only have a HTTP server for data but not a HTTP client for data.
I think this would make CouchDB even more suitable for couchapps.
Now the whole app can be replicated and every couchdb instance can make it's
own HTTP requests and we no longer have to have a node.js server just to
support basic HTTP requests.
> Send data
> ---------
>
> Key: COUCHDB-1219
> URL: https://issues.apache.org/jira/browse/COUCHDB-1219
> Project: CouchDB
> Issue Type: New Feature
> Reporter: Johnny Weng Luu
> Priority: Minor
>
> With CouchDB the application server landscape has changed. The database can
> now handle almost all logic that is data related, eg. validation, updating,
> formatting etc.
> It has a HTTP server for incoming requests but one thing I find missing is a
> HTTP client that can push data to other servers.
> What I have to do right now for sending data to an external service is to
> setup a (node.js) server that listens on the _changes feed.
> When there is a document meant for being delivered through email, node.js
> will send a HTTP request to the (sendgrid) email service.
> I think it would make sense if CouchDB could make HTTP requests on document
> changes, meaning we can eliminate that extra HTTP client layer just for
> sending the data.
> Why only have a HTTP server for data but not a HTTP client for data.
> I think this would make CouchDB even more suitable for couchapps.
> Now the app can be offline. We send an email and it will be sent by couchdb
> when Internet connectivity is there.
> Also now the whole app can be replicated and every couchdb instance can make
> it's own HTTP requests and we no longer have to have a node.js server just to
> support basic HTTP requests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
