Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re^4: precalculating event dates vs.recalculating them.

by samtregar (Abbot)
on Jun 24, 2008 at 16:30 UTC ( [id://693771]=note: print w/replies, xml ) Need Help??


in reply to Re^3: precalculating event dates vs.recalculating them.
in thread precalculating event dates vs.recalculating them.

I'm anticipating very few customers with very many recurrence rules.

Well in that case why bother? It hardly matters what approach you take if you're not planning for lots of users. Surely your server has the power to compute tons of calender data for just a few users.

Aside from that, what you're saying almost makes sense... But I have a nagging sense that the case you're presenting isn't actually possible. So much work that your server can't do it, but so little work that you should hand it off to some Javascript to run on the client. I just can't imagine when that would be the case, but perhaps I'm getting too used to having really beefy servers.

When I think of client processing power I picture my parent's last PC - an Athlon 1800 with 256MB of RAM being slowly choked to death by XP and a collection of useless desktop widgets. The disk was chugging basically constantly during web browsing. Let's just say there wasn't a lot of spare power left for unnecessary Javascript!

-sam

  • Comment on Re^4: precalculating event dates vs.recalculating them.

Replies are listed 'Best First'.
Re^5: precalculating event dates vs.recalculating them.
by roboticus (Chancellor) on Jun 24, 2008 at 16:44 UTC
    I'm anticipating very few customers with very many recurrence rules. Well in that case why bother? It hardly matters what approach you take if you're not planning for lots of users. Surely your server has the power to compute tons of calender data for just a few users.

    Heh ... I didn't mean the system would have very few customers: I meant many customers, but only a few with a *lot* of recurrence rules (i.e. enough to be a burden to a minimally-configured client).

    But I have a nagging sense that the case you're presenting isn't actually possible. So much work that your server can't do it, but so little work that you should hand it off to some Javascript to run on the client. I just can't imagine when that would be the case, but perhaps I'm getting too used to having really beefy servers.

    You're probably right. It's getting difficult to *not* have a beefy server any longer.

    ...roboticus

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://693771]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (5)
As of 2024-04-19 16:41 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found