occasionally connected application design problem

2013-03-27 Thread Greg Harris
Dear People, I need some help to get some good ideas for a design issue I am facing… The application will be geographically dispersed and only occasionally connected to the internet with a slow / unreliable connection. The users at remote branch offices are doing daily data entry to their own

Re: occasionally connected application design problem

2013-03-27 Thread Corneliu I. Tusnea
Greg, I'm sure the SQL guys will tell you about some "magical tool" that can do all of this for you hands free and without any headaches (fingers crossed) but my take would be the good old REST API model. 1. For every Table have two columns LastUpdated, LastUploaded and LastDownloaded. Every chan

Re: occasionally connected application design problem

2013-03-27 Thread David Rhys Jones
This is just an Idea, Message Queues, - pick your flavor. Server and Clients have incoming queues. the server queue thread turns continuously listing to it's incoming queue and post backs all the updates / insert / deletes to the client queues (except the one making the update); the clients con

Re: occasionally connected application design problem

2013-03-27 Thread Craig van Nieuwkerk
That's basically what the SQL Server Replication does, so why not use that. I have used replication over a dial up connection in the olden days, so it is possible with ordinary connections. Craig On Wed, Mar 27, 2013 at 9:06 PM, Corneliu I. Tusnea wrote: > Greg, > > I'm sure the SQL guys will te

Re: occasionally connected application design problem

2013-03-27 Thread Andrew McGrath
Another option is Microsoft Sync Framework - version 2 also works with non-MS data sources. Andrew From: "David Rhys Jones" Sent: Wednesday, March 27, 2013 8:39 PM To: "ozDotNet" Subject: Re: occasionally connected application des

RE: occasionally connected application design problem

2013-03-27 Thread Greg Low (GregLow.com)
201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: <http://www.sqldownunder.com/> www.sqldownunder.com From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Corneliu I. Tusnea Sent: Wednesday, 27 March 2013 8:07 PM To: ozDotNet Subject: Re: occasiona

RE: occasionally connected application design problem

2013-03-27 Thread Heinrich Breedt
; ** ** > > Greg > > ** ** > > Dr Greg Low > > ** ** > > 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913fax > > > SQL Down Under | Web: www.sqldownunder.com > > ** ** > > *From:* ozdotnet-boun...@ozdotnet.com [m

RE: occasionally connected application design problem

2013-03-27 Thread Katherine Moss
net.com<mailto:ozdotnet-boun...@ozdotnet.com>] On Behalf Of Corneliu I. Tusnea Sent: Wednesday, 27 March 2013 8:07 PM To: ozDotNet Subject: Re: occasionally connected application design problem Greg, I'm sure the SQL guys will tell you about some "magical tool" that can do all of

RE: occasionally connected application design problem

2013-03-27 Thread Heinrich Breedt
dnesday, March 27, 2013 2:12 PM > *To:* g...@greglow.com; ozDotNet > *Subject:* RE: occasionally connected application design problem > > ** ** > > Ravendb with replication might be an option > > On 28 Mar 2013 02:05, "Greg Low (GregLow.com)" wrote:** &

RE: occasionally connected application design problem

2013-03-27 Thread Katherine Moss
NoSQL, is it? From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Heinrich Breedt Sent: Wednesday, March 27, 2013 5:13 PM To: ozDotNet Subject: RE: occasionally connected application design problem Yes On 28 Mar 2013 06:33, "Katherine

RE: occasionally connected application design problem

2013-03-27 Thread Heinrich Breedt
tnet-boun...@ozdotnet.com] *On Behalf Of *Heinrich Breedt > *Sent:* Wednesday, March 27, 2013 5:13 PM > *To:* ozDotNet > *Subject:* RE: occasionally connected application design problem > > ** ** > > Yes > > On 28 Mar 2013 06:33, "Katherine Moss" wrote:*

Re: occasionally connected application design problem

2013-03-27 Thread Corneliu I. Tusnea
om > > ** ** > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Corneliu I. Tusnea > *Sent:* Wednesday, 27 March 2013 8:07 PM > *To:* ozDotNet > > *Subject:* Re: occasionally connected application design problem > >

Re: occasionally connected application design problem

2013-03-28 Thread Wallace Turner
an Tax Act that >> cover the definitions of the word “pudding”. I shudder to think what that >> cost us all to have that written . >> >> ** ** >> >> Regards, >> >> ** ** >> >> Greg >> >> ** ** >> >> Dr Greg

Re: occasionally connected application design problem

2013-03-28 Thread Greg Harris
Thank you people, specifically Corneliu and Dr Greg, I think that I have decided to use either Microsoft Sync Framework ( http://msdn.microsoft.com/sync) or a “roll my own” solution. My initial gut is feeling is that with the Microsoft Sync Framework I would be using a steam hammer to crack a nut

Re: occasionally connected application design problem

2013-03-28 Thread Corneliu I. Tusnea
Greg, Looks ok to me. In step 2 I would change to LastDownloadTime and LastUploadTime so you can run the two steps separately if you need to and keep separate times. Remember, the server is always passive, it should never care what a client has or did except for statistical or reporting purposes.