Was originally thinking it might not hurt to leave it in (in spite of new global identity/lookup based approach), but realizing it confuses things for P2P.
Some users have seen some bugs as a result of this (they are using identity for client -> server, but obviously not server -> client since that hasn't been generalized yet). So perhaps in the short term, we could fix this problem for them by making sure we don't send :dat.sync.remote.db/id to the server with the globalize-datoms function, just as we did with the old apply-remote-tx! function.
Was originally thinking it might not hurt to leave it in (in spite of new global identity/lookup based approach), but realizing it confuses things for P2P.
Some users have seen some bugs as a result of this (they are using identity for client -> server, but obviously not server -> client since that hasn't been generalized yet). So perhaps in the short term, we could fix this problem for them by making sure we don't send
:dat.sync.remote.db/idto the server with theglobalize-datomsfunction, just as we did with the oldapply-remote-tx!function.