On 2/7/07, Ray Burkholder [EMAIL PROTECTED] wrote:
Going back to this thread, http://www.kx.com/ deals in financial transaction
databases where they store millions of ticks. They appear to have a
transactional based language with a solution that appears to be robust and
fail resistant.
I'm
Going back to this thread, http://www.kx.com/ deals in
financial transaction
databases where they store millions of ticks. They appear to have a
transactional based language with a solution that appears
to be robust and
fail resistant.
hmm, that is quite interesting. and apparently
On Wed, Feb 07, 2007 at 06:25:41PM -0800, Mike Lyon wrote:
Their gateway is blocking mail from my host. Of course, there is no
clueful contact info on their webpage...
I know you asked for off-list, but since this (mail to Verizon
refused) is a recurring problem, I'm sending this on-list as
On 7-Feb-2007, at 15:24, virendra rode // wrote:
Looking at these attacks, F in particular, if my memory serves me
correct, there are 35 f-root anycast nodes deployed. Maybe this helped
in some respect.
Dave Knight's lightning talk in Toronto seemed to indicate that F's
anycast platform
On 2/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Going back to this thread, http://www.kx.com/ deals in
financial transaction
databases where they store millions of ticks. They appear to have a
transactional based language with a solution that appears
to be robust and
fail
MSN / Hotmail Email admin, please contact me off-list.
Thanks,
James
Other than give them the bum's rush! what do you do when a vendor is
a PITA about SLAs for outages? Obviously there's not enough on the
table to get lawyers involved, but it's aggravating when first they
act like they lost your SLA request, then claim their logs don't match
your logs in some
Find a new vendor is certainly one solution.
Regards,
chad
From: [EMAIL PROTECTED] on behalf of Barry Shein
Sent: Thu 2/8/2007 3:00 PM
To: nanog@merit.edu
Subject: Question about SLAs
Other than give them the bum's rush! what do you do when a vendor is
a
On Thu, 08 Feb 2007 19:09:34 PST, Chad Skidmore said:
Find a new vendor is certainly one solution.
Your current vendor probably knows how much it would cost for you to move to
another vendor (quite possibly to more significant digits than *you* know).
They also know exactly how much they're
Agreed, any termination liability is something to consider. You also
need to consider the impact to your business that the SLA violations is
causing and how that might translate to dollars.
Documentation is going to be key if the vendor is nickel and diming you.
If you have solid documentation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
An SLA is a contract.
A contract is... a contract.
Read it carefully. :-)
- - ferg
- -- Chad Skidmore [EMAIL PROTECTED] wrote:
Agreed, any termination liability is something to consider. You also
need to consider the impact to your business
11 matches
Mail list logo