this paper was submitted on
1 point (100% like it)
1 up vote 0 down votes

papers

subscribe8 readers

Welcome to the public review site of papers appearing in MobiSys 2012. Here you can find the public review written by a PC member for each paper and the authors' rebuttal to it. You can comment on any of them or add your own opinion. Finally you can vote to "like" or "dislike" a paper by clicking the up or down arrows next to its title.

all 6 comments

[–]ConferenceQA 0 points1 point ago

sorry, this has been archived and can no longer be voted on

Q: (Stefan, MSR) TCP aspect. Counter code: aspect implement the counter Different code file than tcp class.

A: Yes.

Q: What does it take to make changes to tcp transmission? Say change to send 2 packets for ACK. Then the developer needs to go to another file and change it. How to keep track of what code needs to be changed in this case.

A: Relying on the file ID.

[–]Christoph_Borchert 0 points1 point ago

sorry, this has been archived and can no longer be voted on

The answer to this question - how to be aware of changing base code that is affected by aspects (known as the fragile pointcut problem) - is actually to rely on IDE support. For Ecplise, there is an AspectC++ plugin that helps the developer to understand the interaction of aspects and ordinary C++ code. Obviously, it is NOT the file ID ;-)

[–]ConferenceQA 0 points1 point ago

sorry, this has been archived and can no longer be voted on

Q: How does this work affect cpu overhead. This is important especially in sensor networks with limited resources. Any numbers?

A: There is no overhead. The work is done in compile time. You are just using the new stack

[–]ConferenceQA 0 points1 point ago

sorry, this has been archived and can no longer be voted on

Q: (MIT) Originally is it that bad for a standard c programmer to modify the files? And you may have to do it for portability anyway. A: You always need to remember this specific structure.

[–]Christoph_Borchert 0 points1 point ago

sorry, this has been archived and can no longer be voted on

This question was about the byte-order conversion via macros, as it is used in uIP, lwIP, Linux and BSD. Yes, this design practice is really bad, since a programmer has to aware of that all the time. If you access packet headers, you MUST NOT forget to surround your code by those macros (htons, htonl, noths, ntohl). This is of course for portability, but via AOP, the same portability is gained by a single aspect that fully encapsulates the byte-order conversion. AOP really simplifies portability in this case.

[–]ConferenceQA 0 points1 point ago

sorry, this has been archived and can no longer be voted on

Q: (Dartmouth) How will the debugging process be impacted?

A: No there is no support. Not needed. There is a direct source to source port. You may debug the generated inter-medium code.