I agree that defining the schema is a good place to start, and that a db backend is the "right thing" to do. For this app though, Postgresql offers some attractive features such as inheritance, stored procedures, and an eclectic set of datatypes.
IANAL but, in this case, i'm pretty sure that yelling "Fire" in the crowded movie house *would* be covered by the 1st ammendment. You're on your own with the arson charges.
RX7's came to the US in 1978 and took 10 seconds to hit 60mph. Sporty yes, fast no.
They redesigned the car for 1986 and offered a turbo version which got to 60 in about 7 seconds. I know two people who had them and thought they were horrible.
The third generation (1992?) cars had twin turbos and did 0-60 in under 6 seconds, but they cost over $30k, which was waaaay too much.
The rotary engines were pretty cool, but they were fuel hogs and prone to catastrophic failure.
Bullshit. Gremlins were very solid and reliable cars, and if you wanted a little oomph, you could opt for the larger 6 cyl engine and a shorter rear gear. If you wanted lots of oomph, you could get a V8. None of them had V6s, all inline.
And there's no reason why the cap shouldn't be applicable to the base allowance. Allow the user to budget his bytes over the month.
Let's say they allow 30G/month. They divide it into 1G/day and increase the cap each day. The user would have the option of dipping into tomorrow's allowance. So if I'm offline on the 1st of the month, I have 2G to play with the next day. OTOH, if I dl a bunch of ISOs on the 1st, I'll have 1G/day for the rest of the month.
This would give the user a way to manage the byte allowance similar to the way they manage the household budget. If the user elects, he can slide the cap right up to the limit (or beyond) and be careful not to run out prematurely.
Slashdot Mirror
"drop the USA vs. Them simplicity."
Right. It's USA+England vs. them.
I agree that defining the schema is a good place to start, and that a db backend is the "right thing" to do. For this app though, Postgresql offers some attractive features such as inheritance, stored procedures, and an eclectic set of datatypes.
I can't attest to how well or poorly they work, but CPAN has Business::UPS and Business::FedEx modules.
perl -MCPAN -e \
'readme Business::UPS;
readme Business::FedEx::DirectConnect;
'
At the request of the package jockeys, UPS engineers are adding a "Squishability factor" to the blocks to make the game more lifelike.
"This is how a dictatorship works, you know? The government makes stupid laws, and there are no independent judges to declare it unconstitutional."
We need some oldstyle patriots (terrorists in modern doublespeak) like James Maddison to straighten this shit out.
"I will likely just burn the whole place down."
IANAL but, in this case, i'm pretty sure that yelling "Fire" in the crowded movie house *would* be covered by the 1st ammendment. You're on your own with the arson charges.
And as a pirate, I'd stick an IR filter on my camera.
"Oh, what a tangled web we weave, when first we practice to deceive."
Yeah, repo man was excellent although I don't remember that line being in it.
Oh well. I'm going to get some sushi and not pay.
It was "Back to the future."
GREEAAAT, 500 it is!
"Legalize it and the money will quit going into the black market."
But then how would Wolfowitz and Cheney fund their next covert regime change in the Republic of Fubar?
And Roadrunner a.k.a. "velocitus
incredibilis".
Beep Beep.
RX7's came to the US in 1978 and took 10 seconds to hit 60mph. Sporty yes, fast no.
They redesigned the car for 1986 and offered a turbo version which got to 60 in about 7 seconds. I know two people who had them and thought they were horrible.
The third generation (1992?) cars had twin turbos and did 0-60 in under 6 seconds, but they cost over $30k, which was waaaay too much.
The rotary engines were pretty cool, but they were fuel hogs and prone to catastrophic failure.
Bullshit. Gremlins were very solid and reliable cars, and if you wanted a little oomph, you could opt for the larger 6 cyl engine and a shorter rear gear. If you wanted lots of oomph, you could get a V8. None of them had V6s, all inline.
"0.0.0.0/1 means any address between 0.0.0.1 and 255.255.255.254"
Shouldn't that be "any address between 0.0.0.1 and 127.255.255.254?"
And there's no reason why the cap shouldn't be applicable to the base allowance. Allow the user to budget his bytes over the month.
Let's say they allow 30G/month. They divide it into 1G/day and increase the cap each day. The user would have the option of dipping into tomorrow's allowance. So if I'm offline on the 1st of the month, I have 2G to play with the next day. OTOH, if I dl a bunch of ISOs on the 1st, I'll have 1G/day for the rest of the month.
This would give the user a way to manage the byte allowance similar to the way they manage the household budget. If the user elects, he can slide the cap right up to the limit (or beyond) and be careful not to run out prematurely.
If you get the chance, check out some of the bizarre contraptions created by Arthur Ganson.
"network transparency is virtually free, especially when the clients and server run on the same machine"
Agreed.
But context switches between the client(app) and server(display) are expensive. Many people seem to mistake this latency for network overhead.
Dual processors are one way to avoid the problem. Direct rendering is another.
Oops. I was thinking of "Lancia".
Funny, but false. Alfa has had several models designated "Beta".
Support NPR
Speaking of w3.org, Amaya has some nice features for working with, and validating complicated document structures.
Just so you know.
Al Gore
CEO, Commode Computer Corporation
"create a webpage that detects a spike..."
mod_tribble?