This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
At my company we've built a fair amount of applications that are hosted in a Windows Service. The clients are pretty much always asp.net web applications and we use remoting to talk to the service. This usually ends up with lots of data transfer objects being sent back and forth, such as args classes, info classes and result classes and eventuates in a lot of code noise! Id like to be able to able to simplify this by using lightspeeds validation capabilities. The problem is that these objects will need to be serialized and remoted, and as lightspeed tracks these changes using the unit of work this will need to be remoted too right? Maybe I check back soon and see what you guys have in regards to WCF, as that is a similar problem. Any help would be appreciated. Cheers
|
|
|
Hi Jake, Generally we would advocate DTO's but we can appreciate the scenario here. You can certainly serialize LightSpeed entities, however as you say you will want to take advantage of the state tracking if possible in a remoted scenario to avoid having to write this yourself :) This is something we intend to support better for LightSpeed 3.0 - we currently have prototyped a sample which remotes the change sets back across to a server side unit of work. If you are interested in having a look at this then let me know and I can email it through to you :)
Jeremy |
|