Konstrukt has a very explicit interface to the http layer, which makes
it quite trivial to substitute. For example, the virtualbrowser
component stubs out the entire http layer, making it possible to run
functional tests without having a web server. You could most certainly
create a web server in php and run Konstrukt on top of that. Whether
that's a good idea is a questionable matter though. Php has a rather
primitive resource management mechanism. Running everything within a
single process would make it very hard not to introduce memory leaks
and concurrency problems.
You received this message because you are subscribed to the Google Groups "Konstrukt" group.
To post to this group, send email to kons...@googlegroups.com.
To unsubscribe from this group, send email to konstrukt+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/konstrukt?hl=en.
Perhaps, but what would the gain be of doing that?
> On a sidenote - the issues that have cropped up during my reasearch into
> this have made me move up my timetable for finding a replacemnent for PHP.
> This is one of the areas that exposes a lot of PHP's weaknesses...
Yes, but in my experience it isn't that much of an issue for most
applications. I think that the simplicity that this design gives is a
very good trade off for some wasted resources.