And the Intel Itanium was among the first. AMD was nowhere close with introducing it unless you are restricting it to the introduction in "Desktop" processors.
Um, are you familiar with IMAP? It leaves a copy of the message on the server, so to benefit one of the "warez guys", all that needs to be done is for someone looking to distribute a program to send it as an email attachment (or multiple separate messages) to the account and then share the login info for the account. Unless google plans on checking users mail (invasion of privacy), then this is a rather easy system for distributing warez as it requires no more than setting a mail client to access the server as IMAP, or as POP3 with "leave a copy on the server" turned on.
From thinking about this dynamic network concept for a minute, I wondered exactly what technology or idea they could use such that routing tables for how to get to a device would change as instantly as the device changes. For wireless, what happens when the device moves between two access points with different network addresses? In order to maintain the shortest/fastest path to the device, does the network communication follow the device between points such that it hops between each point until it gets to the device? Or do the routing tables for how the communication gets to the device have to change as instantly as the device did from pointing to one access point to another and then propagate this change out to the remainder of the network so that the "on-time" nature of the network is preserved and the communication isn't trying to catch up to the end-point?
Slashdot Mirror
And the Intel Itanium was among the first. AMD was nowhere close with introducing it unless you are restricting it to the introduction in "Desktop" processors.
Um, are you familiar with IMAP? It leaves a copy of the message on the server, so to benefit one of the "warez guys", all that needs to be done is for someone looking to distribute a program to send it as an email attachment (or multiple separate messages) to the account and then share the login info for the account. Unless google plans on checking users mail (invasion of privacy), then this is a rather easy system for distributing warez as it requires no more than setting a mail client to access the server as IMAP, or as POP3 with "leave a copy on the server" turned on.
From thinking about this dynamic network concept for a minute, I wondered exactly what technology or idea they could use such that routing tables for how to get to a device would change as instantly as the device changes. For wireless, what happens when the device moves between two access points with different network addresses? In order to maintain the shortest/fastest path to the device, does the network communication follow the device between points such that it hops between each point until it gets to the device? Or do the routing tables for how the communication gets to the device have to change as instantly as the device did from pointing to one access point to another and then propagate this change out to the remainder of the network so that the "on-time" nature of the network is preserved and the communication isn't trying to catch up to the end-point?