5 ms·

is there a more interesting use-case than status updates?

by lucio 12y ago

FuckGo 12y ago
Are you seriously so dense that you can't figure out what you could use this for? No, this is not useful for something that doesn't change over time, yes, this can be used in any case where content changes ever. The home page of your blog updating when a new article is posted? Check. Same for comments on said blog. Hacker news upvote counter changes? Sure. I can't fathom how someone is so dumb to see "cache invalidation of web data" and jump to "can this be used for anything but status updates?". The article was already plenty generic and you're just being one dense motherfucker who happened to latch onto their chosen example and ignore the underlying point.
Xorlev 12y ago
Pretty much any and all data can be cached locally. Any modern application running in a web browser will have state that can change external to the application.
slezakattack 12y ago
Hi, I'm an engineer at IMVU. We use this for almost everything! Status updates is a pretty simple example but we constantly invalidate data for things such as user's list of friends, credit balance, and our real-time chat.
jwatte 12y ago
Suppose I spend some credits to buy some new accessory for my avatar, and then put n that accessory. My credits balance updates. My inventory updates. My avatar product set updates. My profile picture updates. The "sold count" of the product in question updates. All of these pieces of data will be available in real time to whomever is interested in them at the time. If we did this with RPC, everything would have to know about everything. As it is, updates to any subset of the live graph is available to anyone who views it. You can try it at m.imvu.com Also, messaging, decoration, online status, ... Lots of data could, and should, be real time! The cool thing is that it all is deployed and works at IMVU scale. Apologies for typos - phone auto correct.

is there a more interesting use-case than status updates?

by lucio 12y ago

is there a more interesting use-case than status updates?

Are you seriously so dense that you can't figure out what you could use this for? No, this is not useful for something that doesn't change over time, yes, this can be used in any case where content changes ever. The home page of your blog updating when a new article is posted? Check. Same for comments on said blog. Hacker news upvote counter changes? Sure. I can't fathom how someone is so dumb to see "cache invalidation of web data" and jump to "can this be used for anything but status updates?". The article was already plenty generic and you're just being one dense motherfucker who happened to latch onto their chosen example and ignore the underlying point.

Xorlev 12y ago

Pretty much any and all data can be cached locally. Any modern application running in a web browser will have state that can change external to the application.

slezakattack 12y ago

Hi, I'm an engineer at IMVU. We use this for almost everything! Status updates is a pretty simple example but we constantly invalidate data for things such as user's list of friends, credit balance, and our real-time chat.

jwatte 12y ago

Suppose I spend some credits to buy some new accessory for my avatar, and then put n that accessory. My credits balance updates. My inventory updates. My avatar product set updates. My profile picture updates. The "sold count" of the product in question updates. All of these pieces of data will be available in real time to whomever is interested in them at the time. If we did this with RPC, everything would have to know about everything. As it is, updates to any subset of the live graph is available to anyone who views it. You can try it at m.imvu.com Also, messaging, decoration, online status, ... Lots of data could, and should, be real time! The cool thing is that it all is deployed and works at IMVU scale. Apologies for typos - phone auto correct.