...but then the Pearl has a far more capable bluetooth stack to begin with. I installed the latest T-Mobile firmware update earlier this week and have had no speed problems when using the phone as a bluetooth modem (only through OS X, as I don't have a Windows laptop).
Does the patent affect the new standard? If so, can the standard be changed prior to ratification to avoid a second round of payments? I've got no problem with CSIRO's patent, but it would seem like a competent standards org should avoid patented material, or have a good reason why they can't.
FWIW, it seems very unlikely that Google will launch an external service using a self-signed SSL cert for protection. GMail's SSL cert is issued by Thawte:
Certificate chain
0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=gmail.google.com
i:/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA
1 s:/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA
i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority
Could be a test cert they're using for the beta, or it could lend weight to the 'internal server' argument. Who knows.
Easy - I once accepted a job porting the back end of a major telemarketing firm's software to AS/400. You know the little pause when you pick up the phone before the prisoner on the other end starts the time-share pitch? Yeah, that's them. I quit after two weeks - and the first week was training.
After all the fuss about building Bluetooth into OS X v10.2, the first models to be released afterwards have no built-in bluetooth? A bit disappointing, that.
Slashdot Mirror
...but then the Pearl has a far more capable bluetooth stack to begin with. I installed the latest T-Mobile firmware update earlier this week and have had no speed problems when using the phone as a bluetooth modem (only through OS X, as I don't have a Windows laptop).
Does the patent affect the new standard? If so, can the standard be changed prior to ratification to avoid a second round of payments? I've got no problem with CSIRO's patent, but it would seem like a competent standards org should avoid patented material, or have a good reason why they can't.
'How to set up a web server to withstand the /. effect' is not a matter of human consensus yet.
I've heard that so many times it's lost all meaning.
BOND!!!
"It's a different kind of tool."
/ducks //Airplane references, mmmm.
FWIW, it seems very unlikely that Google will launch an external service using a self-signed SSL cert for protection. GMail's SSL cert is issued by Thawte:
Certificate chain
0 s:/C=US/ST=California/L=Mountain View/O=Google Inc/CN=gmail.google.com
i:/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA
1 s:/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA
i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority
Could be a test cert they're using for the beta, or it could lend weight to the 'internal server' argument. Who knows.
Really, why do we need another codec?
Easy - I once accepted a job porting the back end of a major telemarketing firm's software to AS/400. You know the little pause when you pick up the phone before the prisoner on the other end starts the time-share pitch? Yeah, that's them. I quit after two weeks - and the first week was training.
After all the fuss about building Bluetooth into OS X v10.2, the first models to be released afterwards have no built-in bluetooth? A bit disappointing, that.
...just check out the Aeron chairs. They'll be bankrupt in a month.