asp.net mvc的属性更改事件 [英] asp.net mvc property changed event

问题描述

我是净桌面应用程序开发人员尝试切换到 ASP.Net MVC （3或4无所谓）。我们有任何通知 GUI 要穿上这组装<α净库/ code>按属性更改活动（或者我们认为有必要为此事的任何其他自定义事件）。

I'm a .Net desktop applications developer trying to switch to ASP.Net MVC (3 or 4 doesn't matter). We have a .Net library which notifies any GUI you want to put on this assembly by Property Changed Events (or any other custom event we deemed necessary for that matter).

这甚至可能不是一个相关的问题，也许是因为它做的 ASP.Net MVC 完全不同，但你如何更新查看接收更改事件一属性后，您的客户端上的浏览器从组装的服务器？我们生成这些事件我们自己的方式。该组件是我们自己的。

This might not even be a relevant question, because perhaps it's done totally different in ASP.Net MVC, but how do you update your View in the browser on your client after receiving a Property Changed Event from an assembly on your server? We generate these events ourselves by the way. The assemblies are our own.

我读过有关部分景色，但我需要考虑这一点。无论我碰到显得那么繁琐。因为它真的直线前进，并在桌面开发简单。所以，我开始怀疑，如果属性更改活动是为Web开发时的路要走。

I've read about Partial Views, but I need to look into that. Whatever I came across seemed so cumbersome. Because it's really straight forward and simple in desktop development. So I'm starting to wonder if Property Changed Events are the way to go when developing for the web.

的思考？链接？来源？我很感兴趣。

Thoughts? Links? Sources? I'm interested.

P.S：见标签什么我要去为我的进一步的理解。

p.s.: See tags for a further understanding of what I'm going for.

推荐答案

HTTP 的世界是完全不同的结果
您请求从服务器（Asp.Net MVC）的东西，你会得到从服务器返回的响应。结果
有没有办法在该服务器可以将用户联系回**结果作为asp.net服务器的响应后，难道不保留任何东西在内存结果
所以在这里你就错了2个方面的结果
1. 属性更改 - 因为响应后，没有什么在服务器的内存中没有模型（对象）所以没什么whoz属性实际上正在改变结果
2.即使ü保持静态的东西，如果改变没有办法为你的客户联系方式返回搜索结果
**有，让您的客户联系背面提供了一些框架和他们通过插座做到这一点或彗星

HTTP world is entirely different
you request something from the server(Asp.Net MVC) and you get a response back from the server.
there is no way in which the server can contact the user back**
as the asp.net server wouldnt keep anything in memory after the response
so here you are wrong in 2 aspects
1. property changes - because after the response there is nothing in the memory of the server there are no models(Objects) so there is nothing whoz property is actually changing
2. even if u maintaining something static if that changes there is no way for you to contact the client back

**there are some frameworks available that allow you to contact the client back and they do this by sockets or comet

这篇关于asp.net mvc的属性更改事件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！