In comp.sys.raspberry-pi, Deloptes   wrote:
> Martin Gregorie wrote:
> > Since the extension calling mechanism exists, it is also possible to
> > write custom extensions in C, Java or any other language you prefer and
> > either embed triggers for them in the web pages you're serving or to call
> > an extension to generate the page text instead of reading it from a
> > filing system.
> I still have the filling you do not use the terms properly, especially the
> term "injection". This is my problem.

Injection is the term that I've seen used.

Basically you have some system that creates or holds precreated pages.
Something else along the way edits those in-transit to include per user
additions, typically ads.

The difference between "injection" and general server-side dynamic (as
you'd have with PHP), is pages to get injection are designed with
specific places for specific types of things to be added, but the
injector does do anything else to the page. It's all about *adding*
stuff, hence *injection*.

The one I worked with was OpenAdStream, 15 to 18 years ago. It ran as an
Apache module and was intended for companies who sold their own ad
inventory. We used it for weird ass page personalization, but not very
successfully. The NYTimes used it for in-house ads at about that same
time, I remember recognizing the artifacts.

It's equally possible to do this sort of work with a whole separate
program or device sitting somewhere in front of your web server, kinda
like Varnish will sit in front of your webserver to act as a cache.

Ad injection can also be done by hostile third parties, and is one of
the things that https works to prevent. Typically those ones have very
naive ad placentment options.

> You also seems to not accept the fact that there are dynamic web pages
> generated by webserver extentions such as the apaches php extention.

These pages are much more sophisticated in power, but are not as sharply
focused on finding the most profitable guess for an ad.

> Please, note that whatever methodology is used, the visitor of a web site
> receives a HTML sent to the browser. The dynamic part is only the
> generation of this HTML opposed to the static content you pretend to be the
> only "true" HTML.

There's not one "true" HTML for a lot of sites. Consider Yahoo or Gmail:
all of the page is customized for a logged in viewer. From email to
list, to preferences on colors, to news stories to show, to ads to
place.

Elijah
------
OAS seems to still exist, but not sure if it's the same product

--- SoupGate-Win32 v1.05