If it's in JavaScript, the source is sitting in your cache.
True, although we'll see if that's useful. It is quite possible to obscure Javascript to a fantastical degree -- some of the better compression programs produce output that could win an obfuscated-code contest in a walk. (At the highest compression levels, the results have left me scratching my head at the idea that it could even execute.)
You could deliver something in Flash or Java that maintains a persistent connection, so that you can push stuff down to the client. 'Course, that means a lot of connections on your end, which gets expensive.
Yeah, that's not likely to be practical. Current plans are for variable-speed polling, sensitive to the context and nature of the conversation...
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: Huh
Date: 2008-05-09 10:04 pm (UTC)True, although we'll see if that's useful. It is quite possible to obscure Javascript to a fantastical degree -- some of the better compression programs produce output that could win an obfuscated-code contest in a walk. (At the highest compression levels, the results have left me scratching my head at the idea that it could even execute.)
You could deliver something in Flash or Java that maintains a persistent connection, so that you can push stuff down to the client. 'Course, that means a lot of connections on your end, which gets expensive.
Yeah, that's not likely to be practical. Current plans are for variable-speed polling, sensitive to the context and nature of the conversation...