|
 |
ado_dotnet thread: iBindingList Implementation required
Message #1 by "Kruse Ludington" <ceo@K...> on Fri, 8 Feb 2002 05:25:46 -0500
|
|
Although the .NET dataview is supposed to get updated dynamically from
changes taking place within a datasource, it does not appear to be working.
I have spoken with the developer of the iBindingList object within
Microsoft, and he is checking to see if there is a patch needed to fix this
bug. He tells me that if I create my own iBindingList object to replace the
default one used by Microsoft, then I can control specifically which changes
to the datasource are automatically propagated to the dataview. Does anyone
have a sample iBindingList implementation ?
- Kruse
Message #2 by Richard Ainsley <rainsley@p...> on Fri, 08 Feb 2002 04:47:42 -0800
|
|
I thought the whole idea of the dataview was that it used a disconnected
recordset? I would not like to lose that very nice feature as it is
difficult to code without this "feature". You can't scale up to any
reasonable number of users without the resordset being disconnected.
As I understand it, you must explicitly request updates.
Dynamic updates are really useful only for a couple of users due to the VERY
high overhead it requires at the server.
----- Original Message -----
From: "Kruse Ludington" <ceo@K...>
To: "ADO.NET" <ado_dotnet@p...>
Sent: Friday, February 08, 2002 2:25 AM
Subject: [ado_dotnet] iBindingList Implementation required
> Although the .NET dataview is supposed to get updated dynamically from
> changes taking place within a datasource, it does not appear to be
working.
> I have spoken with the developer of the iBindingList object within
> Microsoft, and he is checking to see if there is a patch needed to fix
this
> bug. He tells me that if I create my own iBindingList object to replace
the
> default one used by Microsoft, then I can control specifically which
changes
> to the datasource are automatically propagated to the dataview. Does
anyone
> have a sample iBindingList implementation ?
>
> - Kruse
>
>
>
$subst('Email.Unsub').
Message #3 by "Ludington, Kruse" <kruse.ludington@c...> on Mon, 11 Feb 2002 13:14:11 -0000
|
|
No, I must not have made myself clear: I said "datasource" below in my message where I meant dataset.
I AM using a disconnected dataset. However, I programmatically update the dataset from a live feed. This is for a high-performance
application displaying live data. In order to not slow down the gui I update the dataset via delegates launched from another thread.
The ibindinglist interface is meant to dynamically propogate changes in the dataset to the gui.
With the above scenario, changes made to the dataset are not propogated to a datagrid, and they are supposed to be. (Also, the grid
is not a pure virtual grid, but we have worked our way around that and that is a different subject.) Microsoft is working on the
problem for us, but have stated that it is not too difficult to replace the ibindinglist interface with one we would write
ourselves.
That is why I need an example of a replacement ibindinglist interface. Anybody have any suggestions as to where I may find an
example of one ?
- Kruse
-----Original Message-----
From: Kruse Ludington <ceo@K...>
To: R. Kruse Ludington <kruse.ludington@c...>
Sent: Sun Feb 10 20:24:35 2002
Subject: FW: [ado_dotnet] Re: iBindingList Implementation required
-----Original Message-----
From: Richard Ainsley [mailto:rainsley@p...]
Sent: Friday, February 08, 2002 7:48 AM
To: ADO.NET
Subject: [ado_dotnet] Re: iBindingList Implementation required
I thought the whole idea of the dataview was that it used a disconnected
recordset? I would not like to lose that very nice feature as it is
difficult to code without this "feature". You can't scale up to any
reasonable number of users without the resordset being disconnected.
As I understand it, you must explicitly request updates.
Dynamic updates are really useful only for a couple of users due to the VERY
high overhead it requires at the server.
----- Original Message -----
From: "Kruse Ludington" <ceo@K...>
To: "ADO.NET" <ado_dotnet@p...>
Sent: Friday, February 08, 2002 2:25 AM
Subject: [ado_dotnet] iBindingList Implementation required
> Although the .NET dataview is supposed to get updated dynamically from
> changes taking place within a datasource, it does not appear to be
working.
> I have spoken with the developer of the iBindingList object within
> Microsoft, and he is checking to see if there is a patch needed to fix
this
> bug. He tells me that if I create my own iBindingList object to replace
the
> default one used by Microsoft, then I can control specifically which
changes
> to the datasource are automatically propagated to the dataview. Does
anyone
> have a sample iBindingList implementation ?
>
> - Kruse
>
>
>
$subst('Email.Unsub').
This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information.
No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately
delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or
indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE
GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE
FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are
those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views
of any such entity.
Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not
constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.
Message #4 by "Kyle" <Kyle@T...> on Mon, 11 Feb 2002 08:23:31 -0500
|
|
Check out VS.NET C# online index for "about IBindingList interface".
There is an example there that might help you.
Kyle
_____________________________________________
Kyle Dunn
Chief Information Officer
Funeral Services, Inc.
xxx-xxx-xxxx x 309
Kyle@F...
-----Original Message-----
From: Ludington, Kruse [mailto:kruse.ludington@c...]
Sent: Monday, February 11, 2002 8:14 AM
To: ADO.NET
Cc: 'rainsley@p...'
Subject: [ado_dotnet] iBindingList Implementation required
No, I must not have made myself clear: I said "datasource" below in my
message where I meant dataset.
I AM using a disconnected dataset. However, I programmatically update
the dataset from a live feed. This is for a high-performance application
displaying live data. In order to not slow down the gui I update the
dataset via delegates launched from another thread.
The ibindinglist interface is meant to dynamically propogate changes in
the dataset to the gui.
With the above scenario, changes made to the dataset are not propogated
to a datagrid, and they are supposed to be. (Also, the grid is not a
pure virtual grid, but we have worked our way around that and that is a
different subject.) Microsoft is working on the problem for us, but have
stated that it is not too difficult to replace the ibindinglist
interface with one we would write ourselves.
That is why I need an example of a replacement ibindinglist interface.
Anybody have any suggestions as to where I may find an example of one ?
- Kruse
-----Original Message-----
From: Kruse Ludington <ceo@K...>
To: R. Kruse Ludington <kruse.ludington@c...>
Sent: Sun Feb 10 20:24:35 2002
Subject: FW: [ado_dotnet] Re: iBindingList Implementation required
-----Original Message-----
From: Richard Ainsley [mailto:rainsley@p...]
Sent: Friday, February 08, 2002 7:48 AM
To: ADO.NET
Subject: [ado_dotnet] Re: iBindingList Implementation required
I thought the whole idea of the dataview was that it used a disconnected
recordset? I would not like to lose that very nice feature as it is
difficult to code without this "feature". You can't scale up to any
reasonable number of users without the resordset being disconnected.
As I understand it, you must explicitly request updates.
Dynamic updates are really useful only for a couple of users due to the
VERY
high overhead it requires at the server.
----- Original Message -----
From: "Kruse Ludington" <ceo@K...>
To: "ADO.NET" <ado_dotnet@p...>
Sent: Friday, February 08, 2002 2:25 AM
Subject: [ado_dotnet] iBindingList Implementation required
> Although the .NET dataview is supposed to get updated dynamically from
> changes taking place within a datasource, it does not appear to be
working.
> I have spoken with the developer of the iBindingList object within
> Microsoft, and he is checking to see if there is a patch needed to fix
this
> bug. He tells me that if I create my own iBindingList object to
replace
the
> default one used by Microsoft, then I can control specifically which
changes
> to the datasource are automatically propagated to the dataview. Does
anyone
> have a sample iBindingList implementation ?
>
> - Kruse
>
>
>
$subst('Email.Unsub').
$subst('Email.Unsub').
This message is for the named person's use only. It may contain
sensitive and private proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you are not the intended recipient, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. CREDIT SUISSE GROUP and each legal entity in the
CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business
units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all
e-mail communications through its networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorized to state them to be the
views of any such entity.
Unless otherwise stated, any pricing information given in this message
is indicative only, is subject to change and does not constitute an
offer to deal at any price quoted. Any reference to the terms of
executed transactions should be treated as preliminary only and subject
to our formal written confirmation.
$subst('Email.Unsub').
Message #5 by "Ludington, Kruse" <kruse.ludington@c...> on Mon, 11 Feb 2002 15:11:38 -0000
|
|
Thanks for your help, we'll check it out !
Wei, this may give a jumpstart...
- Kruse
-----Original Message-----
From: Kyle <Kyle@T...>
To: ADO.NET <ado_dotnet@p...>
Sent: Mon Feb 11 08:23:31 2002
Subject: [ado_dotnet] RE: iBindingList Implementation required
Check out VS.NET C# online index for "about IBindingList interface".
There is an example there that might help you.
Kyle
_____________________________________________
Kyle Dunn
Chief Information Officer
Funeral Services, Inc.
xxx-xxx-xxxx x 309
Kyle@F...
-----Original Message-----
From: Ludington, Kruse [mailto:kruse.ludington@c...]
Sent: Monday, February 11, 2002 8:14 AM
To: ADO.NET
Cc: 'rainsley@p...'
Subject: [ado_dotnet] iBindingList Implementation required
No, I must not have made myself clear: I said "datasource" below in my
message where I meant dataset.
I AM using a disconnected dataset. However, I programmatically update
the dataset from a live feed. This is for a high-performance application
displaying live data. In order to not slow down the gui I update the
dataset via delegates launched from another thread.
The ibindinglist interface is meant to dynamically propogate changes in
the dataset to the gui.
With the above scenario, changes made to the dataset are not propogated
to a datagrid, and they are supposed to be. (Also, the grid is not a
pure virtual grid, but we have worked our way around that and that is a
different subject.) Microsoft is working on the problem for us, but have
stated that it is not too difficult to replace the ibindinglist
interface with one we would write ourselves.
That is why I need an example of a replacement ibindinglist interface.
Anybody have any suggestions as to where I may find an example of one ?
- Kruse
-----Original Message-----
From: Kruse Ludington <ceo@K...>
To: R. Kruse Ludington <kruse.ludington@c...>
Sent: Sun Feb 10 20:24:35 2002
Subject: FW: [ado_dotnet] Re: iBindingList Implementation required
-----Original Message-----
From: Richard Ainsley [mailto:rainsley@p...]
Sent: Friday, February 08, 2002 7:48 AM
To: ADO.NET
Subject: [ado_dotnet] Re: iBindingList Implementation required
I thought the whole idea of the dataview was that it used a disconnected
recordset? I would not like to lose that very nice feature as it is
difficult to code without this "feature". You can't scale up to any
reasonable number of users without the resordset being disconnected.
As I understand it, you must explicitly request updates.
Dynamic updates are really useful only for a couple of users due to the
VERY
high overhead it requires at the server.
----- Original Message -----
From: "Kruse Ludington" <ceo@K...>
To: "ADO.NET" <ado_dotnet@p...>
Sent: Friday, February 08, 2002 2:25 AM
Subject: [ado_dotnet] iBindingList Implementation required
> Although the .NET dataview is supposed to get updated dynamically from
> changes taking place within a datasource, it does not appear to be
working.
> I have spoken with the developer of the iBindingList object within
> Microsoft, and he is checking to see if there is a patch needed to fix
this
> bug. He tells me that if I create my own iBindingList object to
replace
the
> default one used by Microsoft, then I can control specifically which
changes
> to the datasource are automatically propagated to the dataview. Does
anyone
> have a sample iBindingList implementation ?
>
> - Kruse
>
>
>
$subst('Email.Unsub').
$subst('Email.Unsub').
This message is for the named person's use only. It may contain
sensitive and private proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you are not the intended recipient, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. CREDIT SUISSE GROUP and each legal entity in the
CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business
units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all
e-mail communications through its networks. Any views expressed in this
message are those of the individual sender, except where the message
states otherwise and the sender is authorized to state them to be the
views of any such entity.
Unless otherwise stated, any pricing information given in this message
is indicative only, is subject to change and does not constitute an
offer to deal at any price quoted. Any reference to the terms of
executed transactions should be treated as preliminary only and subject
to our formal written confirmation.
$subst('Email.Unsub').
This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information.
No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately
delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or
indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE
GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE
FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are
those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views
of any such entity.
Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not
constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.
|
|
 |