You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by fa...@gmail.com on 2011/05/11 14:09:35 UTC
Res: [Analytics---CouchDB] Why go through php? (#1)
Hello mchahn,
My first intention was to create a real access log from one specific website.
When defining the architecture I had problems to register new documents using only jscript. This problem was related to crossdomain requests using only jsscript, so I did a a workaround because my first objective was doing tests with a a huge among of data stored into couchdb.
The idea now is to create other logger tools in python an jscript.
Regards,
Fabio batalha
------Mensagem original------
De: mchahn
Para: fabiobatalha@gmail.com
Assunto: [Analytics---CouchDB] Why go through php? (#1)
Enviada: 10 Mai, 2011 18:55
Your analytics looks interesting. I'm curious as to why you chose to go through php instead of going directly to couchdb? If you went directly from the web page everything would be written in javascript and there would be less load on the server.
--
Reply to this email directly or view it on GitHub:
https://github.com/fabiobatalha/Analytics---CouchDB/issues/1
Enviado do meu BlackBerry® da TIM
Re: [Analytics---CouchDB] Why go through php? (#1)
Posted by Jason Lane <ja...@googlemail.com>.
https://github.com/joyent/node/wiki/modules :)
On 11 May 2011 22:10, Jason Lane <ja...@googlemail.com> wrote:
> why not look at NodeJS?
>
> http://nodejs.org/
>
>
>
> On 11 May 2011 13:09, <fa...@gmail.com> wrote:
>
>> Hello mchahn,
>>
>> My first intention was to create a real access log from one specific
>> website.
>>
>> When defining the architecture I had problems to register new documents
>> using only jscript. This problem was related to crossdomain requests using
>> only jsscript, so I did a a workaround because my first objective was doing
>> tests with a a huge among of data stored into couchdb.
>>
>> The idea now is to create other logger tools in python an jscript.
>>
>> Regards,
>> Fabio batalha
>> ------Mensagem original------
>> De: mchahn
>> Para: fabiobatalha@gmail.com
>> Assunto: [Analytics---CouchDB] Why go through php? (#1)
>> Enviada: 10 Mai, 2011 18:55
>>
>> Your analytics looks interesting. I'm curious as to why you chose to go
>> through php instead of going directly to couchdb? If you went directly from
>> the web page everything would be written in javascript and there would be
>> less load on the server.
>>
>> --
>> Reply to this email directly or view it on GitHub:
>> https://github.com/fabiobatalha/Analytics---CouchDB/issues/1
>>
>>
>> Enviado do meu BlackBerry® da TIM
>
>
>
Re: [Analytics---CouchDB] Why go through php? (#1)
Posted by Jason Lane <ja...@googlemail.com>.
why not look at NodeJS?
http://nodejs.org/
On 11 May 2011 13:09, <fa...@gmail.com> wrote:
> Hello mchahn,
>
> My first intention was to create a real access log from one specific
> website.
>
> When defining the architecture I had problems to register new documents
> using only jscript. This problem was related to crossdomain requests using
> only jsscript, so I did a a workaround because my first objective was doing
> tests with a a huge among of data stored into couchdb.
>
> The idea now is to create other logger tools in python an jscript.
>
> Regards,
> Fabio batalha
> ------Mensagem original------
> De: mchahn
> Para: fabiobatalha@gmail.com
> Assunto: [Analytics---CouchDB] Why go through php? (#1)
> Enviada: 10 Mai, 2011 18:55
>
> Your analytics looks interesting. I'm curious as to why you chose to go
> through php instead of going directly to couchdb? If you went directly from
> the web page everything would be written in javascript and there would be
> less load on the server.
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/fabiobatalha/Analytics---CouchDB/issues/1
>
>
> Enviado do meu BlackBerry® da TIM