Monday, 29 January 2018

Difference between ASP.NET and PHP??

PHP
PHP is a server-side scripting language that has its main implementation in web development. However, it can be used as a general-purpose programming language. PHP was originally created by Rasmus Lerdorf in 1995 and it is currently managed by The PHP Group. PHP originally stood for Personal Home Page, however it was later renamed. It now stands for PHP: Hypertext Preprocessor, a recursive acronym. PHP is free software released under the PHP License, as is incompatible with the GNU General Public License (GPL) due to restrictions on the usage of the term PHP.
PHP is an open source, server-side, HTML embedded scripting language. It can basically perform any task that other CGI programs can, but it is mainly used to create dynamic Web pages. Its main advantage is that it is compatible with many types of databases. Furthermore, PHP can talk across networks using IMAP, SNMP, NNTP, POP3, or HTTP.
PHP includes a command-line interface capability and can be used in standalone graphical applications. PHP commands can be embedded directly into an HTML source document rather than calling an external file to process data. In the HTML document, the PHP script is enclosed within special PHP tags. Due to these tags, the programmer can alternate between HTML and PHP instead of having to rely on heavy amounts of code to output HTML. Also, as PHP is executed on the server, the client cannot view the PHP code.
ASP.Net
ASP stands for Active Server Pages. It is commonly known as Classic ASP or ASP Classic. It is a server-side scripting environment that is developed and released by Microsoft. It was Microsoft's first server-side script engine for dynamically generated web pages. ASP was originally released as part of the Windows NT 4.0 Option Pack. It was meant to be an add-on to Internet Information Services (IIS). Since, then ASP has been superseded by ASP.NET, another product by Microsoft.
ASP is mainly used to create and run dynamic, interactive Web server applications. It also allows one to combine HTML pages, script commands, and COM components to create interactive Web pages and powerful Web-based applications. It also makes it easier to develop and modify the said Web applications.
After its original release, there have been two version releases. The ASP 2.0 introduced six built-in objects to the original, which were Application, ASP Error, Request, Response, Server, and Session. ASP 3.0 introduced some additional enhancements such as Server.Transfer method, Server.Execute method, and an enhanced ASP Error object. Additionally, ASP 3.0 also enabled buffering by default and optimized the engine for better performance. However, as of May 2013 there are no planned upgrades to ASP.
Few More Differences:
Ø  PHP is a free open source platform while .NET is a paid Microsoft platform. PHP is a mix between a programming language and a web framework whereas .NET is a straight application framework.
Ø  Operating system strength of PHP is more than ASP. PHP can be easily use on Linux, Unix and Windows operating system while ASP is mostly used on Windows operating system as it is developed by Microsoft.
Ø  Many auxiliary and assembling features like ftp, email sharing and encryption system is already included in PHP, which are totally neglected in ASP.
Ø  Both ASP and PHP are the technologies of ’90s. PHP regularly released its latest version within short intervals of time and remain up to date with latest development requirements. While ASP had been dysfunctional since 2000.
Ø  PHP performance and code speed is faster and easier than ASP.
Ø  Microsoft Visual Studio 2010 is used as a platform for ASP developers while Eclipse Helios 2010 is used as a platform for PHP developers.
Ø  Sql server 2008 is used as a database server for ASP and MySQL database server is used for PHP.
Ø  Although PHP is simple easier than ASP but functions and controls of ASP are more efficient and reliable than PHP.


Difference between Server-Side and Client-Side Routing

Routing

Routing is the mechanism by which requests are connected to some code. It is essentially the way you navigate through a website or web-application. By clicking on a link, the URL changes which provides the user with some new data or a new webpage.




Server-side

When browsing, the adjustment of a URL can make a lot of things happen. This will happen regularly by clicking on a link, which in turn will request a new page from the server. This is what we call a server-side route. A whole new document is served to the user.
A server-side request causes the whole page to refresh. This is because a new GET request is sent to the server which responds with a new document, completely discarding the old page altogether.

Pros

  • A server-side route will only request the data that’s needed. No more, no less.
  • Because server-side routing has been the standard for a long time, search engines are optimised for webpages that come from the server.

Cons

  • Every request results in a full-page refresh. That means that unnecessary data is being requested. A header and a footer of a webpage often stays the same. This isn’t something you would want to request from the server again.
  • It can take a while for the page to be rendered. However, this is only the case when the document to be rendered is very large or when you have slow internet speed.

Client-side

A client-side route happens when the route is handled internally by the JavaScript that is loaded on the page. When a user clicks on a link, the URL changes but the request to the server is prevented. The adjustment to the URL will result in a changed state of the application. The changed state will ultimately result in a different view of the webpage. This could be the rendering of a new component, or even a request to a server for some data that the application will turn into some HTML elements.
It is important to note that the whole page won’t refresh when using client-side routing. There are just some elements inside the application that will change.

Pros

  • Because less data is processed, routing between views is generally faster.
  • Smooth transitions and animations between views are easier to implement.

Cons

  • The whole website or web-application needs to be loaded on the first request. That’s why the initial loading time usually takes longer.
  • Because the whole website or web-application is loaded initially, there is a possibility that there is data downloaded for views you won’t even come across.
  • It requires more setup work or even a library. Because server-side is the standard, extra code must be written to make client-side routing possible.
  • Search engine crawling is less optimised. Google is making good progress on crawling single-paged-apps, but it isn’t nearly as efficient as server-side routed websites.

UOG CGPA Calculator


Designed for UOG Rawalpindi campus.

Current CGPA:
Total credit hours :

No.   Grade Point * Credit Hours = Grade Points
1    * =
2    * =
3    * =
4    * =
5    * =
6    * =
7    * =
8    * =
9    * =
10   * =
Sum
GPA
CGPA

Tech UOG