Can application designed based on MVC pattern for web should be called web application?

[AspDotNetDev]

ShabanaParveen wrote:

I would be very much obliqued

I'd be obliged if you'd post a video of that for us all to see. Be safe though... sounds painful.

Somebody in an online forum wrote:

INTJs never really joke. They make a point. The joke is just a gift wrapper.

[Lost User]

No. I am working on a web application that uses the MVP pattern (similar to MVC) but no HTML, no JavaScript and, best of all, no browser. Edit: There also is no Flash, Silverlight or any other of the usual suspects :)

And from the clouds a mighty voice spoke:
"Smile and be happy, for it could come worse!"

And I smiled and was happy
And it came worse.

[Rob Grainger]

CDP1802 wrote:

I am working on a web application that uses the MVP pattern (similar to MVC) but no HTML, no JavaScript and, best of all, no browser.

That sounds like an Internet application but not a web application to me. What defines a web application - to me it is use of web technologies. At a minimum HTTP, but generally I'd guess at HTML as well.

[Lost User]

It uses webservices, so there you have your HTTP. The application logic and data access layer on the server can be used just as well if we decided to throw away the client and the webservice and use webpages in the presentation layer again. It behaves like a web application, it uses web technologies for everything but presentation and the data access and application logic layers are identical. I sure think that this a web application and I'm glad not to be limited to HTML and webpages.

And from the clouds a mighty voice spoke:
"Smile and be happy, for it could come worse!"

And I smiled and was happy
And it came worse.

[Chris Maunder]

Is the application creates a browser then by all means, call it a browser application. If it's simply used by a browser, then I'd call it a web application if it's being access via the web. If you're thinking "yes, but I use a browser to access the app" then we not just go to the source and call it a computer application.

cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP

[Shabana Parveen]

Yes, it's simply used by a browser, but its controller class is derived from HTTPController and we can directly put our code in controller and update the view without doing anything on traditional ASP.NET events and it will update the view and display in browser. Oh yes, it can be called computer application instead.

[Shabana Parveen]

What I found while working on it and in msdn that it enforces us to use HTML controls than server controls... Though we can use server controls. Only one plus point I can see is rendering will be fast due to use of HTML control.

[Shabana Parveen]

Sure, i will post the video link very soon...

[Shabana Parveen]

yes, sure there is wonderful Introduction video by Scott Hanselman... http://channel9.msdn.com/Blogs/matthijs/ASPNET-MVC-2-Basics-Introduction-by-Scott-Hanselman[^] He has explained so very nicely but only confusion is whether it is a traditional web application. WebForms are going away as it still uses webforms but events are approached in a different way here!!!

[Shabana Parveen]

I saw people rating as one!!! y so, i only asked a question to clear my view point by receiving other's opinion, is that so very wrong to get 1 vote...

[Shabana Parveen]

Hi Rob, U will like this link: http://channel9.msdn.com/Blogs/matthijs/ASPNET-MVC-2-Basics-Introduction-by-Scott-Hanselman[^][^] Please go through it...