﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administering / SQL Server 2005  / Trading Application / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 20 Jun 2013 04:18:38 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Trading Application</title><link>http://www.sqlservercentral.com/Forums/Topic462712-146-1.aspx</link><description>Sorry, just re-read the pos and saw that it is a web application! Check out [url]www.oilspace.net[/url] and sign up for an online demo, I think it might be similar to what you want to do.Regards,S Armondi</description><pubDate>Wed, 05 Mar 2008 04:20:26 GMT</pubDate><dc:creator>samuele.armondi</dc:creator></item><item><title>RE: Trading Application</title><link>http://www.sqlservercentral.com/Forums/Topic462712-146-1.aspx</link><description>Hi there,Continous DB connectivity is a bad idea, as it ties up resources and (as mentioned) suffers from socket issues. If this is a desktop app, consider creating a server (I usually use a windows service) which will be responsible for receiving the data feed from the source and notify the clients. This can be done using many technologies, but I favour remoting with custom event sinks. Then in your server have a routine which will every so often (5 minutes, 30 seconds, however often you choose) save all your current orders to the DB.If this is a web app, the same applies, but you will have to develop a client-side Javascript engine to either keep a permanent connection open to the server or query the server at a specified interval (say every 2 seconds) to check if updates are available.Hope this helpes,S Armondi</description><pubDate>Wed, 05 Mar 2008 04:18:12 GMT</pubDate><dc:creator>samuele.armondi</dc:creator></item><item><title>RE: Trading Application</title><link>http://www.sqlservercentral.com/Forums/Topic462712-146-1.aspx</link><description>You should consider using something like www.LightStreamer.com or http://www.cognethos.com  to provide Connectivity to your server.  The expectation of a trading app is realtime updates.  A socket app will have issues with firewallsWe have developed numerous trading applications and direct connectivity to the DB is a bad idea.</description><pubDate>Tue, 04 Mar 2008 09:37:54 GMT</pubDate><dc:creator>Tito Toro</dc:creator></item><item><title>RE: Trading Application</title><link>http://www.sqlservercentral.com/Forums/Topic462712-146-1.aspx</link><description>I think this is a real tricky question to ask, and I'll doubt you'll get an answer. Web connectivity usually uses disconnected record sets so real time will need continous connections and a way to force client updates. Other than that I can offer no other thoughts, sorry.</description><pubDate>Mon, 03 Mar 2008 12:51:57 GMT</pubDate><dc:creator>colin.Leversuch-Roberts</dc:creator></item><item><title>Trading Application</title><link>http://www.sqlservercentral.com/Forums/Topic462712-146-1.aspx</link><description>Hi,We are developing a real time trading application. The real time stock quotes feed will be received as inserts into the SQL Server 2005 DB.We should be developing an application that will connect to the DB, The traditional methods to access DB(communication will be over web) seems to be not providing tick by tick updates to clients.I need to know if there is any workaround to handle tick by tick updates using DB. Do we need to develop sort of a middle ware to handle connections with the SQL Server DB and use socket programming to access data? Thanks</description><pubDate>Fri, 29 Feb 2008 15:10:23 GMT</pubDate><dc:creator>MK-660751</dc:creator></item></channel></rss>