That's what .NET RIA Services do: http://archive.msdn.microsoft.com/RiaServices
On Mar 14, 12:33 pm, Ador <[email protected]> wrote: > Hello everyone, > > I am making a client-server application and using NHibernate 3.0. > I need to provide to the end user dynamic filtering capabilities. > Until now I have been using Linq to create predicates for filtering > but now for this application the client (web server) is communicating > with the server through services and so I need to be able to serialize > the request. Thus Linq doesn't work in this senario. > > I have considered the Criteria and HQL methods but I don't want any > NHibernate related stuff to leak to the client. > > I also have seen people using property names and values pairs or the > Example feature of NH to pass criteria but this doesn't cover cases > like : { Customer.Name = "CustomerName" OR Customer.Area = "London" } > where the criteria are not AND and may have complex logic. > > Is there a best practice for this case? > > Thank you -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
