PoNG: 10 Reasons to Rethink the Web - Versionsgeschichte

Mh am 2. April 2014 um 04:53 Uhr

2014-04-02T04:53:08Z

Mh: /* Portal Projects */

2014-04-02T04:51:41Z

‎Portal Projects

Mh am 1. April 2014 um 03:52 Uhr

2014-04-01T03:52:13Z

Mh am 1. April 2014 um 03:50 Uhr

2014-04-01T03:50:22Z

Mh am 1. April 2014 um 03:47 Uhr

2014-04-01T03:47:22Z

Mh am 1. April 2014 um 03:46 Uhr

2014-04-01T03:46:53Z

Mh am 1. April 2014 um 03:44 Uhr

2014-04-01T03:44:37Z

Mh: /* Client Computing Power */

2014-03-31T18:27:25Z

‎Client Computing Power

Mh am 31. März 2014 um 18:24 Uhr

2014-03-31T18:24:47Z

Mh: /* Scaling of Dynamic Web Sites */

2014-03-31T18:24:16Z

‎Scaling of Dynamic Web Sites

@@ Zeile 1: / Zeile 1: @@
 Classic ''portal servers'' or ''web application servers'' create HTML server side. I strongly belive, this is not an up to date architecture. I propose a ''portal web app''. But [[PoNG]] is even more: a ''meta portal web app''. Meta means, that it is no specific ''web app''. It is more a framework, which enables you to create any ''web app'' you need.
-''Meta web app'' sounds complicating. But things get easy, if you don't need to write HTML code server side. Of course you still may need central data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
+''Meta web app'' sounds complicating. But if you don't need to write HTML code server side, things get easy. Of course you still may need central data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
 My top reasons to have a ''portal web app'' like [[PoNG]]:

@@ Zeile 43: / Zeile 43: @@
 == Portal Projects ==
-I've seen and done a lot of web application programming projects. We have JPA and a lot of good frameworks, but crunching good HTML is still a lot on programing work.
+I've seen and done a lot of web application programming projects. We have JPA and a lot of good frameworks, but crunching good HTML is still a lot of programing work.
-−
 == MVC Life Cycle ==
 Do you know how Inter Portlet communication work the JEE way, or MVC is done in JSF? Forget it. Everything is so easy, if the state is maintained only on the client. No sessions, no synching of states in a server cluster, no MVC patterns beween client and server. In the past, you had to use e.g. stateful session beans or session variables of a PHP script. Think stateless!! And please persist information, which are important to remember asynchronous e.g. shopping baskets. This leads to web applications with a good architecture, web applications with a good performance and results in a good user experience.

@@ Zeile 1: / Zeile 1: @@
 Classic ''portal servers'' or ''web application servers'' create HTML server side. I strongly belive, this is not an up to date architecture. I propose a ''portal web app''. But [[PoNG]] is even more: a ''meta portal web app''. Meta means, that it is no specific ''web app''. It is more a framework, which enables you to create any ''web app'' you need.
-''Meta web app'' sounds complicating- But it is so easy to set up your portal, if you don't need to write HTML code server side. Of course you still may need central data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
+''Meta web app'' sounds complicating. But things get easy, if you don't need to write HTML code server side. Of course you still may need central data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
 My top reasons to have a ''portal web app'' like [[PoNG]]:

@@ Zeile 1: / Zeile 1: @@
-Classic ''portal servers'' or ''web application servers'' create HTML server side. I strongly belive, this is not an up to date architecture. I propose a ''portal web app''. But [[PoNG]] is even more: a ''meta portal web app'': With meta I mean, it so no specific ''web app'', it is more a framework, which enables you to create any ''web app'' you need.
+Classic ''portal servers'' or ''web application servers'' create HTML server side. I strongly belive, this is not an up to date architecture. I propose a ''portal web app''. But [[PoNG]] is even more: a ''meta portal web app''. Meta means, that it is no specific ''web app''. It is more a framework, which enables you to create any ''web app'' you need.
-''Meta web app'' sounds complicating, but it is so easy to set up your portal, if you don't need to write HTML code server side. Of course you still may need cenral data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
+''Meta web app'' sounds complicating- But it is so easy to set up your portal, if you don't need to write HTML code server side. Of course you still may need central data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
-My top reasons to have a "portal web app" like [[PoNG]]:
+My top reasons to have a ''portal web app'' like [[PoNG]]:
 == Scaling of Dynamic Web Sites ==

← Nächstältere Version		Version vom 1. April 2014, 03:47 Uhr
Zeile 1:		Zeile 1:
−	Classic ''portal'' ~~servers~~ or ''web application'' ~~servers~~ create HTML server side. I strongly belive, this is not an up to date architecture. I propose a ''portal web app''. But [[PoNG]] is even more: a ''meta portal web app'': With meta I mean, it so no specific ''web app'', it is more a framework, which enables you to create any ''web app'' you need.	+	Classic ''portal servers'' or ''web application servers'' create HTML server side. I strongly belive, this is not an up to date architecture. I propose a ''portal web app''. But [[PoNG]] is even more: a ''meta portal web app'': With meta I mean, it so no specific ''web app'', it is more a framework, which enables you to create any ''web app'' you need.

	''Meta web app'' sounds complicating, but it is so easy to set up your portal, if you don't need to write HTML code server side. Of course you still may need cenral data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.		''Meta web app'' sounds complicating, but it is so easy to set up your portal, if you don't need to write HTML code server side. Of course you still may need cenral data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.

← Nächstältere Version		Version vom 1. April 2014, 03:44 Uhr
Zeile 1:		Zeile 1:
		+	Classic "portal" servers or "web application" servers create HTML server side. I strongly belive, this is not an up to date architecture. I propose a "portal web app". But [[PoNG]] is even more: a "meta portal web app": With meta I mean, it so no specific web app, it is more a framework, which enables you to create any web app you need.
		+
		+	Meta web app sounds complicating, but it is so easy to set up your portal, if you don't need to write HTML code server side. Of course you still may need cenral data stores and logic in the backend, where "application servers" are built for. The AS will also thank you for getting rid of all the HTML stuff. Don't understand me wrong: HTML is perfect to do its job in the browser and the best thing we have in the net, but don't create HTML server side, only to wrap information.
		+
	My top reasons to have a "portal web app" like [[PoNG]]:		My top reasons to have a "portal web app" like [[PoNG]]:

@@ Zeile 33: / Zeile 33: @@
 == Client Computing Power ==
-The times of limited client computing powers are over. Today every new mobile phone or table has 1000 times more computing power than the first WWW server, a NEXT.
+The times of limited client computing powers are over. Today every new mobile phone or table has so many more computing power than the first WWW server, a NEXT.
 == Architecture in Sync With Smartphone Apps ==

← Nächstältere Version		Version vom 31. März 2014, 18:24 Uhr
Zeile 1:		Zeile 1:
−	My top reasons to have a "portal" web app:	+	My top reasons to have a "portal web app" like [[PoNG]]:

	== Scaling of Dynamic Web Sites ==		== Scaling of Dynamic Web Sites ==

@@ Zeile 16: / Zeile 16: @@
 What are the facts:
-* If it really dynamic, the server has to render the page for each client individually -- for each request.
+* If it is a really dynamic scenario, the server has to render the page for each client individually -- for each request.
 * Clients have more computing Power than the server, all clients in summary factors better
 * The net traffic round about 1000 times higher in the classic case, since HTML is so huge, compared with the raw data