It is going to be a kind of subjective question but still want to raise it here.
I am planning to build a stream wall like fb, which will contain objects like text post, * embedded videos*, pictures, polls etc. As I only have bit knowledge in ASP.NET webforms I am planning to use the same. My question is which technique/approach is most appropriate to design the stream?
Will it be good to choose Web API on ASP.NET webform or should I have to rely only on ASP.NET MVC? How can I display different objects type in a same list (stream)? Which I believe is not possible with datalist, repeater, gridview etc.
Perhaps, this seems like a subjective question but may have a value with a perception of architecture.
MVCandHTML 5.HTML 5wan't on your list so it needs particular attention. Facebook's new asynchronous look and feel is primarilySignalR.SignalRis a socket tool for efficient streaming of asynchronous data (en.wikipedia.org/wiki/SignalR). MVC is preferable to Web Forms b/c with or without Web API (i say with) you get a highly sacalable environment that can already send streams of data to the client with JSON action mthds.