ThingML / Kevoree port mapping

HEADS-project / heads_ide

http://heads-project.eu

9 stars 2 forks source link

ThingML / Kevoree port mapping #84

Closed brice-morin closed 8 years ago

brice-morin commented 8 years ago

Currently, in ThingML/KevoreeJS, ThingML ports are systematically split (to avoid serializaing metadata for routing and allow connection to external services). In the case where two Kevoree ports are actually connected to HEADS component, we should not split ports and serialize those metadata.

Mapping policy:

non connected standard port will not be split
port connected with an external connector over kevoree will be split

brice-morin commented 8 years ago

@kehusa would that be ok?

brice-morin commented 8 years ago

@kehusa can you test? As I mentionned in my commit message, I did not test in depth. I can try to test a bit more tomorrow...

kehusa commented 8 years ago

I will do.

ons. 9. des. 2015, 16:27 skrev Brice Morin notifications@github.com:

@kehusa https://github.com/kehusa can you test? As I mentionned in my commit message, I did not test in depth. I can try to test a bit more tomorrow...

— Reply to this email directly or view it on GitHub https://github.com/HEADS-project/heads_ide/issues/84#issuecomment-163291491 .

brice-morin commented 8 years ago

Obviously, it still needs some work. I'll notify you when you can test.

brice-morin commented 8 years ago

By default, port are not split To split a port (and expose raw data without serialization overhead):

    connector myInstance.myPort over kevoree