name publish doesn't instantly update the cache entry in the local node

[fazo96]

When ipfs name publish finishes, it doesn't instantly update the cache of the local node.

This is a problem in my app: the user updates his profile, but it takes a while (around 20 seconds) until he sees his changes.

[jbenet]

i've noticed this before, it's silly.

[harlantwood]

Both IPNS publishing and resolving seemed surprisingly slow in our ad hoc testing (on 0.3.9). For our nascent app, we are moving to tracking the IPFS "head" at the application level instead.

We would much rather use IPNS, and plan to move to it when performance improves.

[fazo96]

@harlantwood it's already improved hugely in 0.3.10 and 0.4.0 in my experience, this is just an issue when you are resolving the address associated with the node that is performing the resolution, which should be an instant resolution but for some reason it's not

[whyrusleeping]

has this been resolved?