opencaching.com

hmarq · Site Admin Joined: 15 Sep 2003 Posts: 351

If a site plans to cache authorizations I have no problem with that, but the initial verification and each subsequent re-verification would be subject to server and network latency/availability.

The authoization caching would need to be cookie based ... passing around credentials in urls is just bad form and begging for impersonation at some poing

CoyoteRed · Joined: 18 Sep 2003 Posts: 220

Yeah, one of the main things I've thinking about is bandwidth.

Someone on the gc.com forums mentioned that if someone tried to duplicate the dataload that Irish handles, one would have to have very deep pockets. They also mentioned that nv.com is where they are because they couldn't handle the load that Irish does.

So, because for the vast majority of people this is a hobby and don't want to spend a lot of money, much less have it to spend, the more we can unload the work from any one server the better. That's why I'm thinking the user cachable URL. They only need to grab it once.

Plus, that's the reason for my push towards smaller, more specialized modules. I could easily handle hosting quite a few caches including the logging scripts.

Offloading like this and using unused hosting space/bandwidth would mean we could handle practically any number of caches--if you consider as you scale up the number of caches you also scale up the number of people willing to take the load.

Something to think about.

CR
_________________
"...been know to miss the finer points."