You have been granted access to this page through First Click Free. Subsequent use of TabbFORUM will require logging in. If you don't have an account, registration is free.
Advertisement
Missing
Steve Jarrett

worldflow

More From
Steve Jarrett

Spotlight-blackInnovations in Trading and Technology

TABB TV Replay: Tablets for Trading
09 November 2012:

This week we bring you our top five most-watched videos since the launch of TabbFORUM. Originally published March 18, 2011: The iPad and other tablets are ideal for sales and marketing but Steve Jarrett, Worldflow CEO, says firms are developing apps just for trading.

Interviewer Gregory Crawford   Source: TABB   Categories: Equities, Derivatives, Technology
Topics: Asset management, Derivatives trading, Equity trading, FX trading, High Frequency Trading, Trading technology infrastructure


Spotlight-white-trans For more videos in the Innovations in Trading and Technology Spotlight Series click here.

Related Videos


Rate This Video

Your Rating
Community Rating 100%

Comments | Post a Comment

3 Comments to "TABB TV Replay: Tablets for Trading":
  • Comment_dan_pt_headshot
    dwatkins

    29 March 2011

    ah makes sense.. good piece. I am wondering if the research data can pull information form a database, say in SQL?

  • Missing
    stevejarrett

    30 March 2011

    In simple terms the iPad or other mobile App can connect directly or indirectly to an SQL database. In terms of the design of our Apps we drive them from a content server, which is exposed as a set of web services to the connected iPad App's. The database behind the content server is an SQL database. So the connection from the iPad(s) of which there may be many, would be through one or more content servers, which provide the content to the iPad's. This allows for caching of results and pre-fetch at the server end, to speed up connections and allow for push. The content server then caches the data for pull from or push to the mobile devices, so an upstream SQL database would be queried by the server, not the Apps directly.. The use of a content server provides for caching, push, security, entitlements, and cuts down the processing on the remote App. But this is our approach, which is designed to remove device specific constraints. Each mobile platform has a distinct development framework, with more or less capability. By building the mobile App using simple frames and web services, allows for device agnostic approaches, and means the server does the "real' work.

  • Missing
    Bart Bartolozzi

    23 May 2011

    Many of our financial market's customers have focused on initiatives related to trader mobility to enhance productivity, but still ring-fenced to the enterprise campus. The challenges of data security/integrity are still being worked through, but there does appear to be more interest in moving in this direction. We are delivering several trader applications that fit logically on Iphones, Ipads and RIM devices, secured and controlled by the business to allow for connectivity in conference rooms and at alternate locations across the campus network. The convenience of these and other applications as they proliferate on trader's Ipad, for example, will naturally "push" the business to support these beyond the campus, in the future.

You must log in to comment.