> You might not have read about dirty schedulers[1] which seem to be a
> stable
> API now, & here's a few links from Steve Vinoski related to NIF handling
> [2][3]
> and some sample code [4] from Steve and from JLouis [5] using them.
Thanks for these links! I think I read something about dirty
sch
> > While it is absolutely possible to link everything into one process,
> > that’s usually not done.
>
> Actually that's what I tried in the very beginning, writing a NIF to
> wrap the ChackraCore API to Erlang functions. While in theory this
> would be possible it's however heavily discouraged b
On Tue, 24 Jan 2017, at 18:24, Daniel Munch wrote:
> Thanks Jan for clearing things up, I couldn't have answered better
> myself! And thanks everybody else for the feedback so far.
>
> >> That clears it up, One more question if I may. In use would this
> >> QueryServer replacement module be an adj
This is really cool!! If you have any feedback for the Chakra team, let me
know and I'd be happy to pass it along. :) I know they're very interested
in getting Chakra adopted as an alternative VM in places where
V8/SpiderMonkey are currently used.
Cheers,
Nolan
-
Nolan Lawson
http://nolanlaws
Thanks Jan for clearing things up, I couldn't have answered better
myself! And thanks everybody else for the feedback so far.
>> That clears it up, One more question if I may. In use would this
>> QueryServer replacement module be an adjacent process to the CouchDB
>> process, or is there some lin
Cool - didn't know that, thanks.
On Tue, Jan 24, 2017 at 6:38 AM, Jan Lehnardt wrote:
>
> > On 24 Jan 2017, at 12:36, Paul Hammant wrote:
> >
> > That clears it up, One more question if I may. In use would this
> > QueryServer replacement module be an adjacent process to the CouchDB
> > process
> On 24 Jan 2017, at 12:36, Paul Hammant wrote:
>
> That clears it up, One more question if I may. In use would this
> QueryServer replacement module be an adjacent process to the CouchDB
> process, or is there some linking fu to make CouchDB and CouchChakra one
> process?
I haven’t looked to c
That clears it up, One more question if I may. In use would this
QueryServer replacement module be an adjacent process to the CouchDB
process, or is there some linking fu to make CouchDB and CouchChakra one
process?
On Tue, Jan 24, 2017 at 6:28 AM, Jan Lehnardt wrote:
> Nice work Daniel!
>
> On
Nice work Daniel!
On 24 Jan 2017, at 02:22, Paul Hammant wrote:
>
> I'm going to be a dumbass here and attempt to paraphrase - pls fix mine up
> so that I may understand it.
>
> You've written a CouchDB clone on top of MS's ChakraCore stack,
He’s re-written the Query Server component of CouchD
Nice work Daniel. If that side of CouchDB interests you, we have an open
ticket on improving the view server protocol.
See this mail[1] and ticket[2]
[1]
http://markmail.org/search/list:org.apache.couchdb-*?q=GSoc+2015+%7C+COUCHDB-1743+Make+the+view+server+%26+protocol+faster#query:list%3Aorg.apa
I'm going to be a dumbass here and attempt to paraphrase - pls fix mine up
so that I may understand it.
You've written a CouchDB clone on top of MS's ChakraCore stack, but it
isn't perfect because a) JavaScript modernized since CouchDB picked and
implementation (and maybe CouchDB should modernize
Hi all,
I just wanted to throw this out into the wild. It is merely a long
week-end hack mainly for learning and fun and I was really happy that
it turned out so nicely so I thought why not sharing it. There isn't
any real intention on using this in production and I rather see it as
a playground f
12 matches
Mail list logo
