Stephan
1) The LPC2XXX package includes GCC, IAR, Keil uVision and Rowleys Crossworks projects. Therefore it should be OK with the MDK-ARM compiler.
2) There are a few OS resources used by the web server and stack so it may not be that easy to separete them. Generally it is intended to be used together as one package.
3) The web server can do quite a lot but isn't standardised (eg. it doesn't support PHP, but can do similar things using its own interface). There are a few posts with examples of typical requirements (mainly displaying and manipulating variables - eg.
http://www.utasker.com/forum/index.php?topic=94.0 ) - dynamic content generation is described here:
http://www.utasker.com/docs/uTasker/uTaskerV1.3_Content_Generation.PDF It interacts with the uFileSystem and user files systems (
http://www.utasker.com/docs/uTasker/uTaskerFileSystem_3.PDF and
http://www.utasker.com/docs/uTasker/uTaskerUserFiles.PDF) and can be used to serve data from an SD card (utFAT -
http://www.utasker.com/docs/uTasker/uTaskerUserFiles.PDF )
It supports basic authentication and post methods - together with the standard user call backs it can then be controlled to do most other forms of protection (eg. individual user access rights on a page basis).
4) Only the V1.4-4B is a Beta (it includes new SDIO controller support) - otherwise V1.4-3 was the last release (including SD card via SPI and utFAT). The Beta versions (or developers version, or pre-release versions) are generally versions made available a.s.a.p. so that the new features can be tested and used, even when the project hasn't otherwise been broadly tested (older versions are always available in case something gets broken in the process).
5) Keil offers a compiler/debugging environment, which should work normally with the project; there are a few Keil specific defines (mainly in LPC23xx.c and sometimes some assembler code) but the rest is not compiler specific.
Keil however is also way a supplier of middle-ware; presumably this is very professional (I believe the price tags are quite high) and could be much better than the uTasker offering - however I don't know any details and it may turn out that it is in fact more restictive than the uTasker solutions. I think that the best thing to do is have a try and see how things go - the uTasker simulator is certainly a hugh plus when working with Web server based projects since it allows fast and efficient development, testing and debugging. The web server is also designed to use low resource levels so should enable much more user sessions that other solutions with constrained memory resources.
You can get an idea of things that can be simply done with the uTasker web server at the on-line demo (
http://demo.utasker.com). There are various projects that have however done much more powerful things with it ;-)
Regards
Mark