Hi Joseph,
I wasn't really looking at any particular single client solution..
If Paul Stovell is listening, what did you use in Bindable Linq.. I am
downloading now to have a look, but thought you may be able to put into
words for larger audience..
thanks
On Tue, Mar 29, 2011 at 9:59 AM,
Ok..
well it looks like bindable linq only propagates changes from what it's got
in memory already, not from changes in the database..
On Tue, Mar 29, 2011 at 9:26 PM, Grant Molloy graken...@gmail.com wrote:
Hi Joseph,
I wasn't really looking at any particular single client solution..
If
[mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Grant Molloy
Sent: Tuesday, 29 March 2011 9:32 PM
To: ozDotNet
Subject: Re: Propagate Database changes to application
Ok..
well it looks like bindable linq only propagates changes from what it's got in
memory already, not from changes in the database
Of Paul Stovell
Sent: Tuesday, 29 March 2011 11:45 PM
To: ozDotNet
Subject: RE: Propagate Database changes to application
Correct, though once upon a time I did have an experiment that worked with
query notifications. From memory you attach some kind of SqlDependency object
to your SqlCommand
-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Paul Stovell
Sent: Tuesday, 29 March 2011 11:50 PM
To: ozDotNet
Subject: RE: Propagate Database changes to application
This is what I was talking about (I think):
http://msdn.microsoft.com/en-us/library/ms172133.aspx
Of *Paul Stovell
*Sent:* Tuesday, 29 March 2011 11:50 PM
*To:* ozDotNet
*Subject:* RE: Propagate Database changes to application
This is what I was talking about (I think):
http://msdn.microsoft.com/en-us/library/ms172133.aspx
Personally I'd probably just poll unless my demand load
[mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Paul Stovell
Sent: Tuesday, 29 March 2011 11:45 PM
To: ozDotNet
Subject: RE: Propagate Database changes to application
Correct, though once upon a time I did have an experiment that worked with
query notifications. From memory you attach some kind
...@ozdotnet.com]
On Behalf Of Paul Stovell
Sent: Tuesday, 29 March 2011 11:50 PM
To: ozDotNet
Subject: RE: Propagate Database changes to application
This is what I was talking about (I think):
http://msdn.microsoft.com/en-us/library/ms172133.aspx
Personally I'd probably
Grant,
Another way to do it would be to push changes to your application based on
an update event occurring in your system. Whenever data changes, publish a
my data has just been updated event and notify your clients of the update.
This would negate the need to do unnecessary polling and remove
I presume SQL Server 2008, so a data driven subscription is probably
your choice.
You will see that MS dropped Notification Services, as no one used it.
Good luck!
Greg Wood
g...@woodgreg.com
0417044439
On Mon, Mar 28, 2011 at 5:06 PM, Stephen Liedig slie...@gmail.com wrote:
Grant,
What type of client is it? Do you control the means by which data is written
to the table? Are clients deployed to the internet or intranet? What kind of
database are we talking about here (I assume you mean SQL Server, since you
mention SqlDependency) but which version?
Joseph
On Mon, Mar 28,
Re: client type - I was more wondering is it a web app? Windows app?
Silverlight? Windows intranet app could do udp broadcast of changes from the
server or something like that.
Sent from my iPhone
On 29/03/2011, at 8:18 AM, Grant Molloy graken...@gmail.com wrote:
Thanks everyone for
Hi list,
I'm looking to have an application automagically update it's view of the
data when the data in the connected database table changes.
I've seen two main ways to do this so far.
1. Poll the database every n seconds
2. Use the System.Web.Caching.SqlDependancy object.
Does anyone else know
13 matches
Mail list logo
