2013-04-10, 23:38
@Fice: I would guess it would be more a push service, but it would work the same in a "pull" scenario. aka the slave finds a master machine and says "what do i need?" rather then a "hey i want this/you need to take this" scenario. I would probably venture to say, if you have the time to implement both ways of doing it. It would be the most beneficial for the end user.
Also, I would probably have setLocalPath as an advancedsettings.xml option, since in general it would be set once for the device, then left alone (EDIT: Or a settings option, if you do need to change it on the fly. Rather then have it in a context menu)
EDIT 2: Another point I would like to make, regarding it being "push" is that, it could work over WAN connections without having to have the end-user do any form of major port forwarding and the likes. Allowing them to gain functionality without compromising their home security. (I have not taken into consideration any random disconnects and devices reconnecting should something fail or just loose connection. If we talking about "mobile" then we have to take into account the best we could get is 3G/EDGE)
Also, I would probably have setLocalPath as an advancedsettings.xml option, since in general it would be set once for the device, then left alone (EDIT: Or a settings option, if you do need to change it on the fly. Rather then have it in a context menu)
EDIT 2: Another point I would like to make, regarding it being "push" is that, it could work over WAN connections without having to have the end-user do any form of major port forwarding and the likes. Allowing them to gain functionality without compromising their home security. (I have not taken into consideration any random disconnects and devices reconnecting should something fail or just loose connection. If we talking about "mobile" then we have to take into account the best we could get is 3G/EDGE)
