Within the last three months, a general-purpose controller was produced along the lines of the CABOOSE project mentioned earlier in this web history. It was written in JAVA and might be combined with a JEE Servlet or a Helidon server using object composition.
As with CABOOSE, it places a partition between the static and dynamic view concerns. So, these might be created in parallel by software team members. This approach greatly simplifies application development.
Simply put, creating a PHDP application requires completing a storyboard of static concerns. One who has placeholders for any dynamic content. The placeholders for the dynamic "hotspots" are replaced in the view is rendered by the controller.
It is deemed general-purpose; because, one might build a vast array of different applications with the same controller mechanism. Which only requires parameterization. In fact, as a simple composable and inheritable object, it might be used among client-side applications.
This application was built using Microsoft Co-Pilot. Who did a wonderful job at suggesting various coding approaches. And, it was built in fewer than forty person-hours with less than a full KLOC during lulls in demand while working as a mathematics tutor at a local community college.
The history behind its development is a very long story. Who actually starts during the early-70s. When, a parent worked at the local medical center and was one of the first research technicians hired who was a person of color.
She offered a suggestion one day during a research seminar, and she was immediately chastised by a doctoral level researcher. Who claimed that research ideas do not come easily. And that, they take a great deal of time developing. She claimed that her son, her only child at the time, could come up with a worthwhile research idea.
At which, the researcher claimed that, if this author produced a fundable research idea before graduating secondary school, he would receive a full scholarship for a college education at the local state university. Which the author did during the Fall of '88. Albeit, he sought an education elsewhere for better or worse.
That confrontation in that weekly seminar, likely on a Friday, during the early-70s set the stage for a single person, this author, having a great influence on modern science and industry. Much, if not all, of the work developing those "suggestions" was done by others, who leaned upon those insights given, were credit them as the "originators" of those ideas. Which was not actually true. They incubated and hatched the products which arose from those ideas. Some of which came from a elementary school pupil.
The idea for a general-purpose controller arose while studying Pascal at Vanderbilt University during the Spring of '89. Seeing that, a starting document was sought for every program that one might write as an undergraduate. One sunny weekend afternoon was spent daydreaming and brainstorming in a dorm-room that was part of the freshman Quadrangle. Having personal contacts among the ranks of the international research community and in senior and executive leadership at SUN Microsystems, many of those ideas were developed. For one, the graduate assistant who taught that Pascal course asked if she could Zerox the notes drawn on pages of the author's research journal. After, some of those ideas were presented during classroom discussions. And, they proliferated through the ranks of computer science and software engineering professors among Vanderbilts departments at that time.
The author and his notes had been the subject of prying eyes. While, he attended secondary school. So, he had learnt that he should keep the best material hidden and non-obvious. Until, he found a serious collaborator. Which was the case for these notes. Which had notions for the feature set of object-orientation, a series of related languages, including JAVA, the rudiments of frameworks and patterns, general-purpose controllers and other novel concepts who have had quite an impact since '90 listed in obvious terms.
In fact, modern computing, including the ACM, have worked diligently at covering over the actual origins of these innovations. For one, they claim that the first OOPSLA conference was in '86. Truth be told, it was during the early-90s. It was the renaming of a conference on software, languages, and programming which focused on structured development that had been occurring since the '70s or '80s. Objects, as abstract data types, did not land upon the computing scene until the Spring of '89. The construct called an object in Simula 67 was simply a dynamic type, like those found in Python 1.0. Which was not a object-oriented language. Objects as abstract data types came in a later version of Python. They have the same name but are entirely different things.
And, many of the "best ideas" had that weekend afternoon were non-obvious concepts hidden behind the surface of the notes recorded. As such, IBM developed a "Domino" server. Who was not built upon a "domino" data structure. Which was seen as a configuration of interacting objects who relied upon dynamic invocation and started with the "initial 'tip' of the first one" yielding a cascade of computational activity. Which would settle upon a result.
Long story short, PHDP was a long-standing idea for a general-purpose controller. Who was a concept called PHP, Cold Fusion, and other "obvious" names in a personal research and idea journal kept during the '90s. These ideas were shared while looking for a collaborator; however, others took what "little information" that they were given and developed what they thought was intended. Which always was much more than needed. As, the source for PHDP and CABOOSE do show.
The source of PHDP might be found here:
complete-web/phdp: HTML Document Preprocessor and General-Purpose Controller for Web Applications