Mainly relaxed parsing rules, some client modifications. Are these changes acceptable for a public release? Is there a better way to make rOCCI compatible with OCCI-OS? Let me know :-)
Fixed check_auth in ClientHttp
check_auth in ClientHttp will now raise an error when it
encounters an unexpected HTTP return code
Allowed Category terms starting with DIGIT
Another attempt to relax term restrictions
Sanitize terms from the relaxed parser
Try to read header Location before uri-list
Sanitize responses from OpenStack
An attempt to further relax parsing rules
Looks good to me, but I would recommend to do a few parsing checks before pulling this request. Changes to the grammar may have strange side effects during parsing.
In the end, we definitely should get rid of ANTLR, maybe I can help with that during this weekend.
Great, I will write a few tests as soon as possible.
We should definitely drop ANTLR but I would like to replace it with something more maintainable than regular expressions. Have you had a chance to look into Ragel or TreeTop?
Fix terms starting with numbers
Updated interactive mode and occi_opts regex
Fixed text/occi rendering to HTTP headers
* Only one value is allowed for Content-Type
* to_header method is fixed, it no longer returns just
links or "" (empty string)
No longer relevant. Closing without merge.