PHP5 Amazon ECS4 (AWS4) API
Thank you for visiting! This is the placeholder for future content regarding the BlindCore project.
If you are interested in reviewing what it might be like to work with BlindCore, you may view some of the generated documentation. Please note that the documentation pages are also only placeholders and the project is still in a planning/alpha phase. This means that any methods or classes can change without notice. The purpose of opening the work is to share ideas, however. So, here they are.
Please note that many of the classes and methods still require a good deal of work. Comments and suggestions welcomed.
For those interested in hacking to or from BlindCore. Also, for discussion of good paths for BlindCore to travel. The direction is open, I hope to make it an important part of your lives with Amazon.
There is a crucial difference between the newest web-service offering from Amazon (ECS4.0) and that is minor versioning. There are other major differences, but this reason is the crux of just why the API should have built under an FOSS license such as the GPL.
The brunt of following the sub-versions to their available featues can be shared amongst the community, as well as lending towards the quality of the coding.
The future I envision for the BlindCore API is one of extreme lightweight running and easy use.
The future should find the project overseeing a two-tier structure for the code in the project: the first is the Core tier. This will be the lone API: small fast, conforms as exactly as possible to the input messages and output messages of the Amazon ECS.
The second tier is called Extensions. I take the "no harm" principle: virtually anything goes here: as long as the community wants it, it isn't too addicting, and it harms no one. This is where the aspects of BlindCore are allowed to look, act, and quack like an application.
I will always be very strict as to what should happen with the core API, while I will be extremely permissive with in extensions.
This is to assure that the core code is general enough to be used in almost any application written in PHP5, and that it really saves time for the community in that "uncoding" others' features is a crude waste of time --- and this is just the issue with code bloat.
I hope this message does well to explain my approach. I am completely open to ideas and will sway and ebb with whatever the community wishes. That is just what this is all about. However, I will enforce structure that I feel will assure the greatest value for all.
