I don't have a feel whether this helps or not
pls understand the mechanism of how a livelink server produces output in the traditional sense.A server side process generates an output html file to a client socket.Before the file hits the client an oscript VM or (java VM if an app server is employed) fills in the server values(oscript language or weblingo as we call it).When all is done browser interprets the html tags and gives the user a view.So if you page viewed a livelink source you will see only javascript or html tags none of the oscript code that generated it.
I do not know much about AJAX and PHP the latter is probably a server side language which may require its own engine to run.
There are some examples invoving AJAX at the knowledge base and I think it is probably client javascript so it should probably run without any concerns.
Typically I have seen examples of Ajax with customviews and
form views in livelink.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937