Skip to content

Commit 9a6593e

Browse files
Copied from api-prototype-6.2.0/meeting-notes
1 parent 308db98 commit 9a6593e

1 file changed

Lines changed: 41 additions & 0 deletions

File tree

meeting notes/2016-10-21.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
*Oct 21st 2016, 6 PM UTC (9PM Finland, 2PM EST, 11AM PST)*
2+
3+
**Attendees:**
4+
- Intel: [Gabriel Schulhof](https://github.com/gabrielschulhof)
5+
- IBM: [Sampson Gao](https://github.com/sampsongao), [Michael Dawson](https://github.com/mhdawson)
6+
- Microsoft: [Taylor Woll](https://github.com/boingoing), [Hitesh Kanwathirtha](https://github.com/digitalinfinity), [Arunesh Chandra](https://github.com/aruneshchandra)
7+
8+
**Topics of Discussion:**
9+
10+
*Module Registration and Initialization*
11+
>Node v0.10 differs from rest of the later Node versions in Module registration and initialization functionality. Is it a good idea to
12+
support Node v0.10 for the prototype effrots considering the additional burden on the API desgin ?
13+
14+
After the debate the consensus was to accomodate this difference in the API design as a way to showcase the resiliancy of the design.
15+
16+
*Concerns about backward compatibility of modules*
17+
18+
Most likely NAPI is going to be introduced in a major Node version which will require modules to be recompiled with NAPI. Having an
19+
explicit field to capture NAPI module registartion is more desirable from a long term maintainenace perspective.
20+
21+
*Indirect dependencies on V8*
22+
>While porting NAPI to Node-ChakraCore using JSRT, Taylor brought up an issue of indirect V8 dependency in NAPI. e.g buffer uses V8 APIs for
23+
construction and initialization. Question was how should NAPI handle such indirect dependencies on V8?
24+
25+
The goal for NAPI is to abstract direct V8-dependecies for native modules. If these high level APIs are dependent on Node structures who
26+
have indirect V8 depdendencies, this should be handled when NodeCore adopts NAPI as part of VM-Nuetralilty. For now Node-ChakraCore should
27+
apply targted shimming approach to make the indirect V8 depdendencies work.
28+
29+
**Action Items:**
30+
31+
1. Module Registration and Initialization for Node v0.10 - Sampson
32+
33+
2. Handle Indirect dependencies on V8 via shim on Node-ChakraCore - Taylor
34+
35+
3. Run perf test on nanomsg - Taylor
36+
37+
4. iotivity conversion - Gabriel
38+
39+
5. Open up known issues on the repo - Arunesh
40+
41+
6. Prepare demo - Arunesh

0 commit comments

Comments
 (0)