linq - Will there be IQueryable-like additions to IObservable? (.NET Rx) -
The new IObservable / IObserver framework in the system. Reactive libraries coming in NET 4.0 are very exciting (see and link).
It may be too early to guess, but will this be the IQueryable-like framework designed for a new terminal?
Instead of a series of calls to get a special case of use, instead of a series of sources, assistance will need to be done in pre-processing events. For example, if you have a very 'chatty' event interface, then using subscribe (). Where (...)
will get all the events through the pipeline and filter the client
What I am thinking is that there will be something similar to the IQueryableObservable, to make these LINQ methods some ' Smart ', which is implemented in the source. I can imagine some network server architecture that can use this framework. Or how about an AD-ON SQL server (or an RDBMS for that matter) that will allow the .NET code to retrieve new data information (triggers in the code) and those notifications require the server's server to be filtered Will be.
OK, you got it in the latest release of RX, which is IQbservable Found in the form of an interface. (Mentioned in the form of IQueryableObservable) remain on the subject for a channel 9 video, coming in the beginning of next week.
To give this feature a little bit, you should understand that there are three orthogonal axes in the Rx / Ix puzzle:
- What You are targeting data models here we look for pull-based versus push-based models. Their relation is based on duality conversions between those worlds (in existence)
- Where you execute the tasks that govern your questions (Sesu Laito). Some operators need concurrency, this is where scheduling and the ISKDular interface come in. Operators are present to hop between concurrency domains (see for example).
- How to execute a query expression is required. Either glossary (IL) or translucent (expression tree). Their relationship is based on homoiconicity conversion is present between both the convergence (such as the encolveable)
all IQbservable interface (which is double for IQueryable and the expression of an IObservable query Tree representation) enables the end point. Sometimes people mislead the work of query translation (to "how to") with the remoting aspects (to run "where"), usually you have some target language (such as for WQL, PowerShell, Cloud Information Services DSLs etc) and remote can be decoupled in both of them, in some target systems, for example, you can local Expression tree to query optimization You can use the rhetoric.
Regarding the possible security concerns, this is no different than the IQueryable capabilities, normally it can only remount the language of one expression and any "really side-effecting" operators (whichever is fundamental This means for languages other than functional ones). In particular, subscribe and operating operations are local and carry you out of Quadable MonD (hence the translation is triggered, such as GetEnumerator in the world of IQueryable). How do you remotely subscribe to something that I will leave the reader's imagination?
Start playing with today and tell us what you think. Discuss some 9 channels of this new feature as well as some discussion of its design philosophy.
Comments
Post a Comment