Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Design in regards to online store
Message
From
10/04/2010 13:52:31
 
 
To
10/04/2010 13:10:00
General information
Forum:
ASP.NET
Category:
Web Services
Environment versions
Environment:
VB 9.0
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01459412
Message ID:
01459557
Views:
27
>>You didn't mention 'till now that you were looking for a generic solution on the web server end. Since you are going to have to install software on each client site I'd put the bulk of the synchonizing logic there since it will be different for each one. This would be responsible for identifying changes in their database and pushing them to the web server database - either directly or via a web service on the web server.
>
>Yes, but in order to be able to do that, it implies that I would have some kind of storage mechanisms locally and this is what I am trying to avoid because I would have to install a database mechanisms, XML or something like that.

Which end are you referring to with 'locally' ?
The in-store system must have a database and, presumably, so does your web server. What additional data storage would you need?

>I would just like to have a Web Service that will collect the keys from the server with the time stamps and act upon that locally to decide what is new, what has to be updated and what has to be removed. As I will have to collect all the keys, I would try to push the synchronization mechanism on an hourly basis. Also, this targets in average between 50 to 1500 items. So, the XML, on an hourly basis, to get the keys shouldn't be that big. The big process will be mostly on the updates. I will have to implement some kind of mechanism, used for the first time, to send the updates in batch, at interval, in order to avoid eating all the bandwidth or the CPU. But, as this initial process is only done once or on recover mode, it doesn't matter that much.

I was assuming you had an SQL DB on the web server. Regardless of how you store the data there my suggestion still makes more sense to me - except you would have to use a web service on the web server rather than accessing the DB directly.
Earlier you said that the clients machines will not have web server capability so that rules out a web service at that end anyway.

In essence you are going to have to write software to monitor for changes on the client database and you are going to have to install some software on the clients machine so why not do the monitoring there? When it detects or decides to push changes have it call a web service on your web server which will be responsible for updating the DB at that end.

>
>>But if customers are not able to order on-line then I don't see why the currency of the web site content is critical - if they pitch up at the store a couple of days later the price and/or availablity could have changed in the meantime anyway...
>
>Yes, that is also a point I tried to discuss. But, they had some kind of concerns about that.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform