RADPHE v0.06 Beta Build 005

Its going to be a while.
Maybe and probably a long while.
You might as well try this one.
And It will Probably fail if I dont release it as a release.
gotta save power.
its only tested on xammp with many modlues disabled...
so who know, it may be totally shattered outside og my testing at some point.
Left Shelter in lue of Fresh Air and a better average of people.

RADPHE v0.06 Beta Build 004

Stealth and Hardening FIX.

Memory Tracking avoids objects, resources, and the site engine, and recursive globals.
If you want to see these things, run a dBug or dBugM or
---- $_INTIN['Dump'][FILE][LINE] and be on DEV Server Config.
OR something.
IF you want the final snapshot of globals you need the PreShutdown event unless you bypassed and canceled the CMS buffer and took over control of the stream, in which case you should include_once dBug_mini and then new dBug($VAR['ViewPoint']); for example.
At current, It doesn't track until $_INTIN['Dump'] and wont display it unless dev config is on your you toggle the memory space on production ideally with some kind binding to your office IP or session and credentials. AKA LOCK IT DOWN.
IT USES MUCH LESS RAM.
TO COME, tracking of namespaces in and after which bench function happens.
TO COME tracking of when functions are made and classes and such.
so it might get interesting if you do nothing to make your app run radphe... but during your code you run it's bench.

RADPHE v0.06 Beta Build 003

Lightweight Again. Sanity Check stepped back.
Memory Tracking limited to 10MB before and 50MB ram free when _INTIN Dump-ing things.
Removed DUMP from every page if disabled and demo files are not deleted.

RADPHE v0.06 Beta Build 002

Lightweight: dont $_INTIN['Dump'][FILE]= do your own dBug and call it smartly on the part of the array you want not the whole thing.
Heavyweight in ram... do the opposite of what i said. But there are sanity checks now... it will not likely fail and it will try to show you what changed when you wanted to dump something because it went wrong.

OK, so filtering globals and fatty memory tracking areas of memory is not working.
because it ends up being by reference to globals and you cant clone everything.
cant test=globals and then test/globals/globals=null even.
SO sanity check is imposed.
It will remember the finishing state of last event for compare to the current finishing state of a event level include.
BUT the last is only if it is under 100mb, then THIS event will compare if less than 250mb ram.
You could at present hit 300mb ram.
this is also because the output from dbug is so big. then history is fully implemented you will have a iframe into a new call that pulls saved work from session or db.
keeping output buffers from bloating.
then if i get array copy filters working and maybe my own array diff...
it should get back to being light weight; and it is if your not debugging.

RADPHE v0.06 Beta Build 001

Memory Tracking and ++
Too warn out to test and maybe further perfect.

RADPHE v0.05.9 More Fixes for dev ability

More Fixes. If you had problems with the dbug and Dump. Or html head linked Virtual Resources used by DOM being pre-expired.
Also if you had issues with being stuck on permeant cached virtual resourced and you dont know to use the conde/network inspector to disable cache in browser for dev to ensure fresh copy. the reason for virtual being permanent is to reduce called to them as they are primarily meant to be static resources. there are Boolean toggles in code to eliminate dynamics and execution in virtual resources. Remember most of your app development is supposed to be on the outside of the site engine as real files and their real resources like normal and then hence you would use the application.php to unify that folder and sub folders. whereby url folders = app or application areas.

RADPHE v0.05.8

More Production Ready and Hardened against probes and spiders. And Documentation.

Production Development Toggle
Rename of /_system/_DevServer.php.disabled
AND optionally Deletion of /-RADPHEindex.php

This is a good release. Vulnerabilities AND "Tells' are fixed. It is possible to conceal that the server is running RADPHE or that target files are there but denied. This build will 404 lie for everything and that is a big deal against being probed with a dictionary of vulnerabilities.

RADPHE v0.05.7

GLOBAL is clean now, its instead $_INTIN[]

RADPHE v0.05.6

Cleanliness, and a fix.
might be last stable for a while.
going to complex the kernel part with more requirements like feeling what events it needs to have and then add some on from there; hence many events will be grouped together and the long route will disappear or you will have to explore it on your own. the long route is terminating the connection in the pre php, ending up in the request php resumed because of include_once then doing it again for the post php and also redirecting output to custom server log file after the first connect termination signal (buffer or stream can still continue after, it needs to time out).
Lets face it... No OnE iS InTeReStEd In ThAt ???

RADPHE v0.05.5

Ever Cleaner, slightly more functional.