search

x42 / syncpop

0 stars 0 forks source link

Handle problem of CPOP having clp data not yet transferred to APOP but moving to new APOP #14

Open bquandt opened 11 years ago

bquandt commented 11 years ago

There is a problem which can occur if CPOP had not yet rsync to it's APOP prior to moving to a new APOP. There are two possiblities, one the clp data will not match the new APOP server (which it shouldn't anyways), and the data will be lost. Second, by accident the timing will match and the CLP data will get matched to the wrong video.

A reasonable simple workaround is to record with the CLP data which APOP it belongs to, and then only rsync to the CLP data for the right APOP when on its network. This also solves the "lost" data problem. Namely clp data will stay on a CPOP until it is reconnected to the APOP it was originally connected to.

x42 commented 11 years ago

related: We need a unique ID for the audiolollipop.

I propose to make APOP hostname == APOP Wifi ESSID. The hostname is also used for the zeroconf .local lookup

Alternatively we can use some UUID, but requires an additional mechanism that allows to query it. The UUID could stay the same even if the APOP is renamed, but I don't see a use-case for that.

re-using the ESSID=hostname would simplify things: we already have a mechanism to change the ESSID, and the CPOP is already configured to use that.