On Monday 10 September 2007 14:23:29 Chenri wrote: > - asynchronous price feed, the server receive price feed to be broadcasted > to all connected clients.
AFAIK, laszlo can only pull data, you won't be able to push into laszlo (but you could try polling). > - high data broadcasting rate, at certain times the rate is high > and also need to be broadcasted instantly (2-3x per seconds) I wouldn't go near laszlo for that kind of speed (how big is your data ?). Actually, I probably wouldn't go near any http-based solution. > - able to generate dynamic charts in line, candlestick based on > the client side from the price feed received Haven't looked at laszlo charts recently, but should be ok. > - can be run at client / don't need to be loaded from the server every time > it want to be used, > is this what it mean by SOLO deployment? SOLO can achieve that, although it's not its only use. > - can have local datastorage, somekind of local temporary database/dataset > to store historical prices, so it can load it from the temporary > database/database and don't need to load from server everytime. Some tricks exist, but they're quite limited AFAIK. Browsers don't like you accessing local data. > - due to the high responsiveness type of the forex trading industry, it > need also quite responsive interface. I've tested some of the sample > application, but they're kinda slow, it could be my internet line though, i > hope someone can pointed at me some examples for the kind of application or > the possibility to do it with lazlo Writing a snappy laszlo app requires either a very small app or lots of work. > To make a better understanding about the system i'm thinking, > consider creating an online stock trading system where users > can see real time prices (asynchronous but capable of high rate speed) > with also real time charts that can went back to see years of historical > prices > and then can orders through the system and can see their online/realtime > account balance. All of that in one screen. Laszlo can make very pretty interfaces, but I think that some of your requirements will be hard to meet. This would be the same with any browser-based technology. > One thing I also want to add is the load burden for providing connection > for something like 1000 simultaneous connection, how many connections > will it provide service per server, i know this is depends on many factors, > but do anyone have a rough estimation or experiences about it? You really want to ask the tomcat or apache guys about that. -- Vincent de Phily
