AOL’s modules use Dojo
Shawn Carnell (one of the folks behind AOL’s coolio modules stuff (see Iamalpha) reports that they met with the Ajaxian dudes.
This meeting bore fruit in a positive review of the usage of Dojo in AOL’s modules.
What I’d love ot hear is their reaction to a core issue that has come up - while developing these modules:
1. So I’m a module developer, I write some php-thingie that does something - based upon my server and I post it to the AOL modules directory.
2. OH MY GOD - I get Slashdotted, or Digged or whatever the current term for ‘incredible amount of response and clicks’ - that bombards my poor little server! Ouch!
3. So now what happens?
a. Success ruins the golden goose and I take down my module?
b. I wait for traffic to subside and breath a sigh of relief?
c. I come up with some way to ‘monetize’ these clicks - and use that money to buy more hardware and pay for bandwidth?
d. Any other recourse?
4. Believe it or AOL is hoping that folks will do all their storage via local Javascript - so that none of the traffic goes back to your server. But that ultimately limits the capability and functionality of your module. I’ve pondered this situation for a while and still don’t have a nice answer - that feels good.
What to do? JSON (I don’t think that changes anything.)
Any other suitable sceanrio any of you can think of?
It’s important - as this AOL module ‘channel’ can be a HUGE distribtuion channel to 10’s of millions of willing end-users (notice BTW that MySpace has nothing like this - yet.)

January 31st, 2006 at 8:08 am
We did this on purpose so we don’t “drown” individual developers’ shared hosting plans. In the past, I’ve seen us drown services with “real” hosting, and I’d hate to do that to someone paying $10 a month (like I do) for shared hosting. We’re not even talking about bandwidth, we’re talking about load, which most hosting providers will take you down for having too much of.
The answer is there is no answer. If you’re going to expose a web service to millions of customers, you have to have the scale to support it. If you don’t, you probably shouldn’t expose it. It’s not egalitarian and doesn’t feel like a satisfactory answer either, but it’s reality.
Which is why module developers should really considering doing mashups of existing web services, either with javascript or XSL. If you’re confident in your hosting plan, by all means, expose a web service, and we’ll see how it fares. You just take a lot of risk on yourself in doing so.
July 21st, 2006 at 1:14 am
free internet hold em pc games
harms red farmhouses chiefly magnetically irregularity?download free internet hold em calculator shareware trial http://www.uniqueinternetholdem.com/free-internet-hold-em.html
August 27th, 2006 at 5:38 am
Texas HoldEm Online Tournaments
overseers methodically assassination railroad chromium,Poquer On Line Tournament http://www.online-674-poker-kiszka-blada.com/poquer-on-line-tournament.html