Ability for the client to asynchronously receive notificaitons from the server whenever the data in the client's context has changed on the server (possibly as a result of another user's action).

Do code generation for WPF the same way Silverlight does (except taking advantage of any WPF-specific features, of course).

Currently, when you apply the Include and Association attributes in the Domain Service MetaData class, you cannot add an association based on a many to many relationship since the keys don't match.

This is very important..creating DTO's at the service just to fullfil some specific view requirements is very painful and incorrect!

We just be able to project entities just like WCF Data Services does.

Prototype/description at http://www.nikhilk.net/RIA-Services-Fluent-Metadata-API.aspx

Support all the types of filtering, updating, etc. that OData supports.

It would be great to extend the current wizard to be able to manage the service visually as the tables change during development.

If we add database entities like tables, views, import stored procedures as functions, VS should automatically update the domain service class, or atleast should ask the user if it should be automatically updated. Some generic error messages for required fields, date time fields as part of validation in Metadata should be generated for required fields and when new tables are added, it should generate for them too.

Propagate authorization/role metadata from server to client so that it can be used for building authorization-specific UI; e.g. admin sees additional named update methods that a user does not.

Enable paging over sprocs / non-IQueryable sources. Map client-side paging infrastructure to DomainService query method parameters.

So that multiple calls to SubmitChanges() of different domain contexts can we wrapped into a TransactionScope()

I am having a hard time with WCF Ria Services without the benefit of EF. When my middle tier is what it is and cannot be modified. Many entities don't serialize using the Xml Metadata Serializer and many features don't work as all sample code I ever seen to find manipulating the data on the client.

Would love to point the RIA Svs Wizard at some mapping file in NHibernate or LLBLgen and have it work, understand entities in the ORM etc.

Use web services returning/consuming DataSet on the server and get DomainContext to provide RIA experience with those web-services.

DomainDataSource Filters should be extensible by allowing new filter classes to be defined, adding onto the EntityQuery. This would allow a custom filter to be created that uses custom logic to manipulate the query, or even have a group of filters with their own And/Or operator.