John,
I understand your thoughts on couchapps, but there are some advantages
so don't dismiss them outright. Some advantages are:
1. Naturally manage code, specifically views, in a directory structure.
2. Easy deployment with .couchapprc.
3. Bootstrap data with _docs/ for testing.
The major disadvantage is that there is no document level read
restrictions with pure couchapps, which is a deal breaker for a lot of
applications. However, this doesn't invalidate any of the advantages
noted above.
If read-level access is a problem, then node-restify or express might
make a nice proxy or api.
If you're writing a cordova app with jQuery Mobile, then you might try
loading your static content locally and persisting data to couch with
ajax via mobileinit.
-zh
On Wed, Aug 15, 2012 at 1:25 PM, Octavian Damiean <mainerror@gmail.com> wrote:
> Well, as with any technology you don't know, take your time to get used to
> it and to fully understand it and then start using it.
> On Aug 15, 2012 7:13 PM, "john.tiger" <john.tigernassau@gmail.com> wrote:
>
>> On 08/15/2012 08:16 AM, Dale Harvey wrote:
>>
>>> You need to have a proxy so you can made requests from your site to the
>>> CouchDB via the same host, then everything 'just works'
>>>
>>
>> hmm, can you explain this a bit more - obviously server-server calls
>> provide security - but where does the proxy fit in ? we have been happy
>> using node-http-proxy (nodejs) on some apps. jquery.couch seems to be
>> something we're looking for making the db calls - frankly, have not had the
>> time to look at it too closely yet - maybe this weekend
>>
>>
>>
>>
|