Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Security Technology

Microsoft Surface To Coordinate SuperBowl Security 218

suraj.sun writes to tell us that in preparation for nearly a quarter of a million people descending on Tampa for the Super Bowl, the Tampa authorities are deploying new tech for security communications and response. All of the incidents and communications will be plotted and tracked on a new implementation of Microsoft's Surface. Hopefully it wont have to reboot after every new incident report. "The Microsoft Surface device will display a Microsoft Virtual Earth map of the entire region tracking events, incidents, resources and tasks in real-time using its unique large display, multi-user, multi-touch and interactive capabilities, also allowing it to communicate with remote devices and PCs. With a quick hand-gesture, the map can zoom in and display a 3D image of the city, including detailed views of buildings and streets and real time resource tracking."
This discussion has been archived. No new comments can be posted.

Microsoft Surface To Coordinate SuperBowl Security

Comments Filter:
  • by eln ( 21727 ) on Friday January 30, 2009 @03:26PM (#26670113)

    Does it interpret a system crash as an attack on central command and launch the missiles?

    Seriously though, this seems as useless as that magic screen thingie they're always playing with on CNN. Sure, it looks pretty, but using brand new technology like this, with its inherent glitches, in a system that you need to be constantly up and highly responsive is not a wise thing to do.

  • Not surprising. (Score:4, Interesting)

    by Kaenneth ( 82978 ) on Friday January 30, 2009 @04:22PM (#26670805) Journal

    A lot of development into touch/multitouch interfaces has been funded by the US military.

    Sand/toxins can get into a keyboard or mouse and be very very difficult to clean out, but a MS Surface type display/input can just be wiped with a damp cloth, sterilized, etc. if you use a low enough power CPU/GPU you could seal the processing components away from hazards as well.

    I doubt the security systems will be public facing, as that would be a security risk... so this probably isn't funded as a promotion by MS, the security folks may actually like it.

  • by Anonymous Coward on Friday January 30, 2009 @07:52PM (#26673267)

    The only Microsoft Surface that I ever saw in person was in the lobby of Microsoft's Bldg. 19 (their HR bldg.) in Redmond. It was used to "wow" potential employees. Problem was the thing kept crashing. The lobby "concierge" told me that "they" were coming out to replace this one again because it had issues. They replaced it during lunch. However, the new one didn't seem to work either.

  • Re:Oh no (Score:4, Interesting)

    by ozphx ( 1061292 ) on Friday January 30, 2009 @10:27PM (#26674309) Homepage

    You mean _Fingerwork's_ tech, which Apple bought, locking out fairly cool tech to their shitty few percent of the market. I'm typing this on a Touchstream LP - which works as a generic HID keyboard/mouse input device with all kinds of delicious gesture recognition. Its a great cross-platform piece of technology, which Apple has now ruined by sitting on a bunch of patents so they can sell more fkn iPhones.

    Now yes, everyone else doing multitouch, like MS and the Lemur guys have to use a substandard implementation.

    Fuckers.

  • Re:Oh no (Score:3, Interesting)

    by causality ( 777677 ) on Friday January 30, 2009 @11:16PM (#26674563)

    Or C) bought cheap memory.

    I've seen too many Windows machines that were unstable due to "cheap memory" that had no problems running Linux to actually believe that explanation. I mean, I know Linux is great but I don't expect it to improve the quality of the hardware.

    For that matter, I've also seen machines with verifiable memory errors (per Memtest86+) that had no problems running Windows and could handle everything except GCC compiles in Linux (the compiles failed with "internal compiler error" every time, which is consistent with a hardware issue). This also harms the credibility of the "cheap memory" excuse for Windows instabilities. I'm not saying that verifiable memory errors could not possibly cause stability problems; if you read this and think that's what I believe, well, you're wrong. They obviously can. I am only saying that I've seen that happen without being a tremendous showstopper, which was rather contrary to my expectations, and that this also renders me disinclined to believe easy explanations from Windows apologists.

    I know that the above is anecdotal. I know that it does not constitute evidence. I don't expect it to convince you or change your mind about anything. I'm just giving a few reasons why lots of people don't believe in that explanation.

"When it comes to humility, I'm the greatest." -- Bullwinkle Moose

Working...