this paper was submitted on
2 points (100% like it)
2 up votes 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 3 comments

[–]ConferenceQA 1 point2 points ago

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

Nicolas, MSRA: So you get one policy for everybody?

Answer: Yes, but we can partition the decision tree per user.

How would it work on a per person basis?

Good question. We haven’t done it yet, but are exploring different policies.

[–]ConferenceQA 1 point2 points ago

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

Jitu, MSR: What is the impact of continuous reads on power consumption?

Once read is issued, sets up soft state in backend server. Whenever writes match predicates, clients are notified. In moving to product, leveraging Yahoo infrastructure. Can use MPNS, etc.

[–]ConferenceQA 1 point2 points ago

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

Rajesh, Singapore: How did you convince Yahoo that this is easier for application developers to use?

Answer: We haven’t done that test yet. API similar to yql (Yahoo query language).

So, you did and np-complete reduction to a yahoo product?

Answer: Yes, no user study yet.