My company is looking to develop a web product that will need to run on both Websphere and IIS. Ideally, we would like to use the same framework for both, but I am currently ignorant of the options, if there are any. On IIS, we would most likely use ASP MVC, and JSP on Websphere. Is there some common technology we could use on both platforms?
IIS is a web server. Websphere (or what just the term Websphere commonly refers to) is an application server, Websphere Application Server (WAS). IIS would be more comparable to IHS (IBM HTTP Server) or Apache HTTP Server.
So the answer to "Is there some common technology we could use on both platforms" is probably JSP since WAS is mostly just a Java application server.
A reference for running JSP on IIS Lightweight servlet engine for serving java application via IIS
Here is a more detailed discussion on application vs web servers
What is the difference between application server and web server?
A more general note: Getting the same application to run exactly the same in both environments will likely be a difficult task for any moderately interesting application.
What would be truly common to both is HTML, CSS, and JavaScript. That is, client-side technologies rather than server frameworks. So I'd recommend at least considering one of the JavaScript MVC frameworks. TodoMVC.com compares several of them.
Related
I am supporting an ancient web application which still uses some VB6 for the data sources behind ASP classic web pages, running on IIS.
Historically we have always loaded the VB6 COM components into COM+, which was considered the best way to make them available to IIS services. I cannot find any reliable documentation on this now - sure I have the management documentation telling me HOW but I'm not sure about WHY, what is best practice, what is required or optional etc.
Has anything changed in recent years? Can we just register the VB6 DLLs and let IIS manage how they are used, or do they need to be put in COM+ for proper threading or pooling etc?
We have 5 IIS servers in a farm, with up to 3000 users at a time. The VB6 data methods are accessing a number of SQL Server databases via ADODB. The DLLs are installed and registered on each server, we don't use DCOM, but load them into a number of application groups in COM+. Servers are Windows Server 2012 R2 with IIS 8.5.
I want to create a progressive web app with ASP.NET CORE 2.0 using Razor Pages preferably because I like the code behind architecture of Razor Pages.
Please recommend me a tutorial or docs or any course where I can begin to learn this. I already know ASP.NET CORE so I don't need to learn that, but actually I want to learn and create PWA but at server side I want to use ASP.NET CORE 2.0 and Razor Pages (if possible). And then I will be hosting them in Azure.
The courses I've searched so far on the web, all of them are with node.js or any other server side technology. Which is a problem because I don't want to use JS, except on the front end, where I don't have a choice.
According to your description, I assume that you could refer to the following tutorials for getting started with PWA using .NET Core:
Yeoman PWA Angular 4 & .NET Core
PWA-Asp.NetCore
Building Progressive Web Applications (PWA) with Visual Studio
This is a very common misconception...that the client-side is tightly coupled to the server-side. They are not.
Your ASP.NET application renders pages/html on demand, at run-time, on the server. The site will work with or without the client-side code, that is why it is progressive....
Your PWA/Service Worker code is only concerned with stuff in the browser. You need to think about it as a stateless concern on the client. The service worker can add a proxy layer to the client-side where you can cache and really perform the task ASP.NET or Node Or PHP, etc perform, just in the browser, before the network must be used.
My advice, to learn the concepts, is to create a static version of your site or a test site. Get comfortable with how to make a PWA and a simple caching service worker, then apply it to your ASP.NET site.
There is nothing in ASP.NET itself your service worker needs to know about, well short of your routes. And your routes are independent of ASP.NET.
I am wondering: why we use to split a web app into a client (JavaScript, CSS or even a framework like React or angular) and a server (PHP)?
Why it is preferable to do so instead of simply going on a website that includes PHP and HTML all together?
scalability and private storage. Hosting your own server side framework allows for huge application and privacy. The storage of html is minimal at best so it is much safer to have your own backend stuff. especially for enterprise software.
My requirement is run an embedded HTML\JS Web applications on a Win CE-ARM device.
We also have a Linux-ARM device for which we used Node js to run any Javascript app that also uses node modules like require,express and such.
Basically, we would like start a node server inside the device that serves HTML/JS pages as in when requested.
Since Win CE -ARM doesn't support node js and porting of node js to Win CE is an humongous task, we are looking for alternatives to node js in Win CE.
I looked up online and found very little on this front.
Basically we want to have a server running inside the device that serves html/js pages as in when requested( Imitate the node behaviour).
Is there any framework available for Win CE?
Any kind of comments or help is appreciated.
Thanks
I am not aware of any frameworks that implement server-side Javascript on Windows CE (you can always serve html/js pages though, if that's what you're after).
Unless you do manage to find a third-party alternative, your options are limited to:
ISAPI extensions
ASP (note: not ASP.NET)
ISAPI extensions are written in C/C++, and are a comparatively primitive environment. This does not necessarily mean a bad environment - whether that's the case really depends on your requirements. We've used ISAPI extensions successfully in a number of products.
The ASP implementation in Windows CE is only a subset of what desktop IIS supports; the linked MSDN pages have all the details about this.
If you don't want to use HTTPD WinCe webserver and to study how primitive and user unfriendly C++ ISAPI environment works, you could implement an extensible web-server in C# for example with RESTFUL webservices.
Refer to this.
You can than use JQuery instead of ASP to create dynamic pages.
If you need also the browser on the device you can use the IESample bundled with WinCE.
I need to create a JSON service to get and post data from a local and remote http/https server on Linux for my mobile apps. -I'm using MySQL as DB engine-
I tried with Glassfish EJB/JSP (I like Java), but it was a kind of frustrating, due the poor support that my linux development machine (mint 13) has for Oracle Glassfish.
In your opinion, what is the best way to make a remote JSON server on that environment? which alternatives do I have?
If you want to accept and send back JSON, you want a JAX-RS-based service, not a JSP one.
You will most likely use Jersey, RESTEasy, CXF, or similar implementations of the JAX-RS specification.
Sending back JSON from a JAX-RS implementation is trivial; that's what JAX-RS is designed to do. Generally speaking, JSP is used for web applications (where HTML, CSS, images, and JavaScript are returned), while JAX-RS is used for RESTful web services, where JSON, XML, and YAML is returned. You can use JSP to produce JSON, but it is not common.
As far as your overall architecture is concerned, any webserver is fine (Apache, Tomcat, etc.) and you can use either Springframework or a full app server like JBoss or Glassfish. Springframework has its own REST support, but I've used JAX-RS several times with Spring and it works very well. Since you already are using Glassfish, integrating a JAX-RS implementation should be straightforward. This article from Oracle shows you how.
Well, I guess you need to find a good framework where you feel confident.
I use Zend PHP + Doctrine to serve my apps. Why? I just create simple controllers in a good MVC like Zend and use all power from Doctrine to handle queries. Ok, but why? Because I develop quick and neat code on it.
Best