Martin Kolárik
Martin Kolárik
>Sent an email, but I think it bounced, so copying to here: (feel free to close whenever) Hi, can you tell me what address you sent the email to? Regarding...
> Do you need any assistance on the feature? (Of course, I'm fine being lazy and waiting weeks/months/whatever for others to do the work, too, haha!) We'll need to do...
@filfreire please check now. We had some `@branch` URLs incorrectly cached at the CDN level for longer than they were supposed to be.
As explained in the readme, purge works only for releases, not branches.
@ElektrikSpark the release numbers need to be valid semver to be considered for `@latest`. As your response headers show, you're receiving the branch files: ``` x-jsd-version: master x-jsd-version-type: branch ```
Upon further consideration, I think, regardless of this issue, it makes sense to have an option for creating separate channels for private rooms. In our scenario, we have ~1k clients...
> Classic socket.emit()'s are not affected though. By this, you mean local emits? If yes, that's right, it only affects emits on remote sockets.
major version pinning is not suitable for production - cache is too long with up to 14 days of cache
Hey, have you tried the purge API? It should work well in this case: https://github.com/jsdelivr/jsdelivr#purge-cache
major version pinning is not suitable for production - cache is too long with up to 14 days of cache
Quick note: the CDN cache time is only 12 hours already, as indicated by `s-maxage`. The problem in your case is indeed likely the client cache.
Hey, thanks for the detailed description. I'll keep this open to consider later, as we were thinking about a similar feature before as well. Unfortunately, I don't think we'll be...