What do you mean what is my problem? I have no problem.
I was purely pointing out that many companies, including id software and borland have chose to distribute a cut down, demo product.
This generally isn't done out of the goodness of their hearts. It's done as a loss leader. In the case of Borland it's see how good our old software is? Buy the latest version at retail price and get the manuals. With id you get extra levels and can use all the player made mods. With Redhat you get some extra cd's of stuff and some support.
We're going with a Datacentre for a number of reasons
* They have 2 Generators and fuel to last indefinately. * They have cold standby network equipment * They have 24h security, video cameras & biometric access. * We can (socially) network with our peers at the datacentre * Good Fire & Environmental Protection * Setting up a datacentre is a lot of hassle for 5 boxes... * Don't need to worry about real estate. * Datacentre has better connectivity than redundant T3's to your office. * Network capacity is cheaper at a datacentre * Better SLA terms at a datacentre
> 1. Cluster the SQL box for high availability and fail-over. MySQL is non trivial to cluster, hence the $$$ Andover is providing to the project. > 2. Switch from NFS to SMB - even the apache site recommends this for speed. Depends on what they are using NFS for... But I think they are generating html pages from the db at fixed intervals and copying to the www servers locally at regular intervals. > 3. Look into having local instances of SQL running on the web-servers - read-only copies that are replicated from the main DB... then the central DB would only be used for write (aka comments and postings...) Thats reliant on being able to use replication which mysql doesn't support - and it's a big nono to put db's on the same machine as the web servers.
Re:Sounds kind of limited to me
on
IP Over SCSI?
·
· Score: 1
I'm a little fuzzy how this works, if one node (tertminology?) was talking to another at 160MB would the whole line be used? If so with 8 devices then performance wouldn't differ greatly from switched ethernet... Also could something like Fibre Channel be employed? expensive I guess:)
Sounds kind of limited to me
on
IP Over SCSI?
·
· Score: 1
I cant see any reason not to use 100Mb ethernet adaptors in a switched environment.
I'm sure if you upgrade to the latest $$$ version of C++ all such restrictions will be removed, it's an old marketing ploy - you couldn't use homemade mods with the shareware version of Quake, upgrade to Blah 98 & receive a neato printed manual etc.
/8's,/16's and/24's the number of bits in an IPv4 address unique to a subnet, ie: 10.x.x.x is a/24 network with 2^24 IP addys 192.168.1.x is a/8 network with 2^8 IP addys
SYN is part of the connection negotiation involved in TCP. Basically SYN flooding is a type of attack where the attacker requests a connection, but doesn't follow through - this means that the target is using all its' resources in servicing non existent requests creating denial of service to legitimate users. Most OS's, Routers, Firewalls etc can deal with this nowadays.
PIX is a Cisco Firewall Product Arrowpoint is a company / brandname for load balancing equipment
RSM & MSFC I don't know, it was explained elsewhere.
CS-100 - a model number of Arrowpoint equipment, I guess rated to handle 100mbits peak traffic.
/8's,/16's and/24's the number of bits in an IPv4 address unique to a subnet, ie: 10.x.x.x is a/24 network with 2^24 IP addys 192.168.1.x is a/8 network with 2^8 IP addys SYN is part of the connection negotiation involved in TCP. Basically SYN flooding is a type of attack where the attacker requests a connection, but doesn't follow through - this means that the target is using all its' resources in servicing non existent requests creating denial of service to legitimate users. Most OS's, Routers, Firewalls etc can deal with this nowadays. PIX is a Cisco Firewall Product Arrowpoint is a company / brandname for load balancing equipment RSM & MSFC I don't know, it was explained elsewhere. CS-100 - a model number of Arrowpoint equipment, I guess rated to handle 100mbits peak traffic.
If you insist on designing software services so easy that an idiot can use them, then expect idiots to use them. Now couple this with a need to "innovate", ie force out upgrades to software with features that people don't need then what do you expect?
If you head over to www.php.net, you'll find a number of freeware projects that do stuff like inventory management, trouble ticketing and web based interfaces to mail, etc - you may find something of relevence there.
.com et all are in the root namespace which is administered internationally,.us is the designated US namespace but unlike other country level domains it is divided by geographical location rather than orginisation.
This is slightly offtopic... we're building a large scale site thats expected to handle 180k pages an hour, the majority of them encrypted with SSL. Our server platform is Solaris, but even with load balancing, I think the servers will choke on this much SSL:)
Does anybody have any experiences with using this kind of solution? and are there any export restrictions etc on the hardware (our company is in the UK)? I'm a little fuzzy about whether the key strength is determined by the hardware, or the software controlling it.
We most probably will use Apache, but NS Enterprise is also an option.
Yahoo! have a category devoted to this stuff, but I didn't know where to start.
Slashdot Mirror
> What is your problem?
What do you mean what is my problem? I have no problem.
I was purely pointing out that many companies, including id software and borland have chose to distribute a cut down, demo product.
This generally isn't done out of the goodness of their hearts. It's done as a loss leader. In the case of Borland it's see how good our old software is? Buy the latest version at retail price and get the manuals. With id you get extra levels and can use all the player made mods. With Redhat you get some extra cd's of stuff and some support.
We're going with a Datacentre for a number of reasons
* They have 2 Generators and fuel to last indefinately.
* They have cold standby network equipment
* They have 24h security, video cameras & biometric access.
* We can (socially) network with our peers at the datacentre
* Good Fire & Environmental Protection
* Setting up a datacentre is a lot of hassle for 5 boxes...
* Don't need to worry about real estate.
* Datacentre has better connectivity than redundant T3's to your office.
* Network capacity is cheaper at a datacentre
* Better SLA terms at a datacentre
> 1. Cluster the SQL box for high availability and fail-over. MySQL is non trivial to cluster, hence the $$$ Andover is providing to the project. > 2. Switch from NFS to SMB - even the apache site recommends this for speed. Depends on what they are using NFS for... But I think they are generating html pages from the db at fixed intervals and copying to the www servers locally at regular intervals. > 3. Look into having local instances of SQL running on the web-servers - read-only copies that are replicated from the main DB... then the central DB would only be used for write (aka comments and postings...) Thats reliant on being able to use replication which mysql doesn't support - and it's a big nono to put db's on the same machine as the web servers.
I'm a little fuzzy how this works, if one node (tertminology?) was talking to another at 160MB would the whole line be used? If so with 8 devices then performance wouldn't differ greatly from switched ethernet... Also could something like Fibre Channel be employed? expensive I guess :)
I cant see any reason not to use 100Mb ethernet adaptors in a switched environment.
I'm sure if you upgrade to the latest $$$ version of C++ all such restrictions will be removed, it's an old marketing ploy - you couldn't use homemade mods with the shareware version of Quake, upgrade to Blah 98 & receive a neato printed manual etc.
doh!, formatting screwed
/16's and /24's the number of bits in an IPv4 address unique to a subnet, ie: 10.x.x.x is a /24 network with 2^24 IP addys 192.168.1.x is a /8 network with 2^8 IP addys
/8's,
SYN is part of the connection negotiation involved in TCP. Basically SYN flooding is a type of attack where the attacker requests a connection, but doesn't follow through - this means that the target is using all its' resources in servicing non existent requests creating denial of service to legitimate users. Most OS's, Routers, Firewalls etc can deal with this nowadays.
PIX is a Cisco Firewall Product Arrowpoint is a company / brandname for load balancing equipment
RSM & MSFC I don't know, it was explained elsewhere.
CS-100 - a model number of Arrowpoint equipment, I guess rated to handle 100mbits peak traffic.
/8's, /16's and /24's the number of bits in an IPv4 address unique to a subnet, ie: 10.x.x.x is a /24 network with 2^24 IP addys 192.168.1.x is a /8 network with 2^8 IP addys SYN is part of the connection negotiation involved in TCP. Basically SYN flooding is a type of attack where the attacker requests a connection, but doesn't follow through - this means that the target is using all its' resources in servicing non existent requests creating denial of service to legitimate users. Most OS's, Routers, Firewalls etc can deal with this nowadays. PIX is a Cisco Firewall Product Arrowpoint is a company / brandname for load balancing equipment RSM & MSFC I don't know, it was explained elsewhere. CS-100 - a model number of Arrowpoint equipment, I guess rated to handle 100mbits peak traffic.
If you insist on designing software services so easy that an idiot can use them, then expect idiots to use them. Now couple this with a need to "innovate", ie force out upgrades to software with features that people don't need then what do you expect?
If you head over to www.php.net, you'll find a number of freeware projects that do stuff like inventory management, trouble ticketing and web based interfaces to mail, etc - you may find something of relevence there.
.com et all are in the root namespace which is administered internationally, .us is the designated US namespace but unlike other country level domains it is divided by geographical location rather than orginisation.
:)
I wonder if term.in.us is available?
This is slightly offtopic... we're building a large scale site thats expected to handle 180k pages an hour, the majority of them encrypted with SSL. Our server platform is Solaris, but even with load balancing, I think the servers will choke on this much SSL :)
Does anybody have any experiences with using this kind of solution? and are there any export restrictions etc on the hardware (our company is in the UK)? I'm a little fuzzy about whether the key strength is determined by the hardware, or the software controlling it.
We most probably will use Apache, but NS Enterprise is also an option.
Yahoo! have a category devoted to this stuff, but I didn't know where to start.