- we do not assume that user will stay connected at all times...we expect users to logoff once they are done
- this product is intended to be used by professional commodity traders
- they will typically login and view a page with the list of commodity contracts that they had setup to view market data for (e.g. Crude near 3 futures contracts, Gas Oil near 3 months futures, etc)
- product will show the current market data and it will update prices in real-time
- to achieve, we thought:
a) it is better to have a persistent TCP connection as against HTTP Connection, so that customer will not miss out any important prices or alerts
b) server can send important alerts & related info directly (push) as they occur without waiting for the client asking for it (pull)
- Our concerns are:
a) Can we develop with an assumption that all service providers allow such connections?
b) Can we use direct J2ME with Netbeans IDE for mobile development? (we had been so far using Blackberry APIs - this solution works only wit Blackberry handsets)
c) Do you recommend any other 3rd party libraries or tools? (so that we need not have to reinvent everything all over again)
Thanks
Main Topics
Browse All Topics
by: MicheleMarconPosted on 2009-01-30 at 02:17:12ID: 23506650
You ask for "persistent" connection. This requires the data connection to never interrupt (i.e. never running out of battery charge and never close the connection).
Assuming that the phone is always powered, you need to take into consideration the cost of your connection (time, data). I don't know of any SP that gives you a true FLAT rate for data connection.
I personally suggest to reconsider the architecture of your product; however the answer of your question is yes for a, b, and c.