|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
Generate data entry and reporting .NET Web apps in minutes, straight from your database. Read our FREE whitepaper “Build Web 2.0 Applications Without Hand-Coding” Download now! |
|
#1
February 19th, 2002, 08:22 AM
|
|||
|
|||
|
co-location trap???
what should we look into very careful in co-location?
no experience with co-location. thanks!
__________________
regards, wish to use AT 89c51 single chip computer to do remote sensing and send the data back from woods to office via nokie 3330 and internet. HOW? first I must revise C program thro' example, what's next?
|
|
#2
February 19th, 2002, 08:40 AM
|
|||
|
|||
|
We went with AT&T for a co location solution. We used Foundry server Irons switches for transparent failover (Radware also makes a product). We have a frame connection from our local data center to AT&Ts and we user rsync to update the remote machines. We also looked @ sungard and sprint but AT&T had the better deal. I think you should first identify what your CO LO requirements are ( i.e geographical diversity, transparent failover) then decide on who best fits your needs.
|
|
| Viewing: Dev Shed Forums > Operating Systems > Linux Help > co-location trap??? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
