LIVE! from San Jose, California: The First Ever Virtual Opening of NASDAQ

Discussion in 'Wall St. News' started by trader99, Aug 9, 2005.

  1. trader99


    August 10, 2005, will mark the first time in 34 years that The NASDAQ Stock Market will conduct opening and closing ceremonies from outside New York. Three thousand miles away at Cisco Systems' San Jose, California headquarters, Cisco and NASDAQ have recreated the MarketSite including a replica blue video wall and electronic podium to mirror the NASDAQ opening and closing bell ceremonies. Cisco CEO, John Chambers, along with 2000 Cisco employees, will ring the bell to signal the start of trading from a "virtual" control center, complete with NASDAQ's famous video wall that provides trading updates throughout the day.

    This historic event is made possible thanks to a dual path, secure, private, IP-network. Cisco's Internet protocol (IP) networking equipment and software will be transmitting NASDAQ trading information from New York to San Jose, highlighting the benefits of virtualization and IP technology for businesses and society. The virtual open event caps off a year of commemoration marking Cisco's 20 years history of giving back to the community, technology innovation and industry leadership.
    Coming on August 10, 2005:

    * Webcasts of the virtual opening and closing ceremonies
    * Webcast and podcast of interactive discussion on virtualization and technology innovation with leading technology executives
    * A Q&A interview with Cisco CEO John Chambers about the event, the importance of virtualization, and Cisco's next 20 years
    * News releases covering the event
    * Results of a Cisco-sponsored innovation poll, conducted by an independent third party
    * Fact sheets about Cisco, NASDAQ, and networking technology
    * Executive biographies and photography
    * Event photography
  2. i wonder how instantaneous the internet really is...

    i was just reading about wireless security protocols (wpa/psk and wep) and read that wpa/psk has noticible latency when applied at the software layer due to the extra encryption/decryption that adds data to the packets.