On 23 Aug 2010, at 13:46, Benoit Chesneau wrote:
> On Mon, Aug 23, 2010 at 1:07 PM, Robert Dionne
> wrote:
>>
>>
>>
>> On Aug 22, 2010, at 4:58 PM, Mikeal Rogers wrote:
>>
>>> One idea that was floated at least once was to replace all the code
>>> currently have on top of mochiweb directly
On Mon, Aug 23, 2010 at 1:07 PM, Robert Dionne
wrote:
>
>
>
> On Aug 22, 2010, at 4:58 PM, Mikeal Rogers wrote:
>
>> One idea that was floated at least once was to replace all the code
>> currently have on top of mochiweb directly with webmachine.
>
> If I recall, Paul Davis did some prototyping
On Aug 22, 2010, at 4:58 PM, Mikeal Rogers wrote:
> One idea that was floated at least once was to replace all the code currently
> have on top of mochiweb directly with webmachine.
If I recall, Paul Davis did some prototyping work on this at one point
>
> This would make extensions and i
> It seems that noone except us is interrestted in that ;)
I'm indeed very interested in that. However, as I won't be able to
contribute much to the refactoring, I didn't feel like having to say
something in this regard. So, nonetheless, here are my two cents.
Recently, I've spent a few hours div
One idea that was floated at least once was to replace all the code currently
have on top of mochiweb directly with webmachine.
This would make extensions and improvements follow already well defined
patterns provided by webmachine.
-Mikeal
Sent from my iPhone
On Aug 20, 2010, at 2:09 AM, Ben
On Sun, Aug 22, 2010 at 7:37 PM, Benoit Chesneau wrote:
> It seems that noone except us is interrestted in that ;) Anyway I'm
> thinking that in case of indexer it would be very useful to have a
> generic way to add some kind of handler allowing any people to plug
> its own stuff to the system ind
On Fri, Aug 20, 2010 at 1:32 PM, Volker Mische wrote:
> +1 for a refactor.
>
> GeoCouch duplicates a lot of code. I tried to keep the names in as similar
> (though meaningful) to the original ones as possible to see where the
> duplicated code is.
>
> I would love to see that everyone who wants a
Hello,
I remember following your great tutorial on how to create a new
indexer (numidx).
A very good way to build a new one, but it did show the internal
architecture needs a serious refactor.
You have the impression everything is spread wherever it might fit.
Also I saw that Riak did such transf
+1 for a refactor.
GeoCouch duplicates a lot of code. I tried to keep the names in as
similar (though meaningful) to the original ones as possible to see
where the duplicated code is.
I would love to see that everyone who wants a new kind of indexer just
need to provide the data structure an
+1
I would change the or in the subject line to and, .ie. do both :)
I think this is an excellent idea and a good time to start this. At a
conceptual level CouchDB is dirt simple internally. This fact and it's use of
Erlang in my opinion should be seen as it's main advantage. One way to leverag
Hi all,
I work a lot these days around the httpd code and the more I work on
the more I think we should refactor it to make it easier to hack and
extend. There is indeed a lot of code in one module (couch_httpd_db)
and recent issue like vhost and location rewriting could be easier to
solve if we
11 matches
Mail list logo
