web application requirement

Discussion in 'Pre-sales questions' started by Ldgi, Jul 1, 2009.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I have a winform application on my server that receive some geodata information by a serial modem

    now i must create a web application that display and handle these data.

    the mattar is : can i load these data as soon as they arrive to my pc into sql server hosted in your sql server using normal sql command so users can navigate data in the web application that i will create?

    if yes how to do ?
    i didnt find any example or 3d in this forum

    thanks
     
  2. How about this for a simple 30 second architecture?

    1) Create a web service with a method that accepts a new geo-data record. You might want to support batch mode depending on the rate of data recieved - if so this does affect your web service method signature and implementation.
    2) Create a DAL that is called from the web service method to perform inserts into your db.
    3) Reference the web service from your existing winform application and call the web service method you created in step (1) with new geo-data records.
    4) Develop the rest of your web application to visualise this data.

    ..job done, or perhaps that's too simple and I really did miss your point entirely.
     
  3. an application can be implemented in many ways

    i just wanna know if i can do in the way that i explained in the first post
    i have only a time constraint problem


    i think about wcf but i havent time to convert my application logic to implementing any type of web seriveces (read debug time too)

    anyway thanks for your post
     
  4. I'm sorry, your project constraints and requirements were not entirely clear in your first post.

    I have assumed that you are (or will be) a DASP customer, your winform application is hosted on your own server, and your web application / SQL Server will be hosted by DASP.

    If this assumption is correct, an even dirtier solution to the web services based solution I first suggested is to directly use ADO.NET over the internet to your SQL Server. Personally I would never implement this type of solution because I'm sure it is not a system architecture you will find documented or recommended as a best practice anywhere..however given your constraints in this project you might decide this is a reasonable approach.
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page