(PigIron servlet)->(gui web app).execute()
PigIron now has a data servlet layer. It still needs the presentation layer.
When I started PigIron in August, I figured that by the end of the year it would be up to the data servlet level. As it is, PigLet, the PigIron servlet is running as of last night.
PigIron now has a data servlet layer. It still needs the presentation layer.
When I started PigIron in August, I figured that by the end of the year it would be up to the data servlet level. As it is, PigLet, the PigIron servlet is running as of last night.
Just HTTP PUT a JSON string to PigLet and PigIron executes the desired VSMAPI function from your JSON description.Now I have to decide how to GUI it. I suppose it's using javascript at some level because it's JSON. The JSON interface wasn't created in conformance to complete model. The only model was the idea that there were one or two data interchange formats that web application writers are using in lively presentation metaphors.
JSON is easy, so PigIron has a JSON layer.
So the question is, what's the easiest way to create the presentation layer? Choices abound, starting with this crude list:
- hand-written html and javascript
- perl cgi
- ruby cgi
- java
The web app is intended to facilitate the composition and execution of complex z/VM provisioning operations built from individual VSMAPI transactions.
I'm one programmer. Reader, what do I choose?
Some previous items about PigIron:
- 11/18/08 PigIron 0.8 released
- 08/18/08 Generating Java from m4 macros
- 08/15/08 PigIron Open Source Java Class Library for VSMAPI
