OpenStack OCCI-OS compatibility hacks #74

Closed
wants to merge 10 commits into
from

Conversation

Projects
None yet
2 participants
Collaborator

arax commented Apr 5, 2013

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 :-)

Contributor

ffeldhaus commented Apr 5, 2013

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.

Collaborator

arax commented Apr 5, 2013

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?

arax added some commits Apr 7, 2013

@arax arax Fix terms starting with numbers 78250c1
@arax arax Updated interactive mode and occi_opts regex 0d54cdb
@arax arax 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)
62d3332
Collaborator

arax commented May 11, 2013

No longer relevant. Closing without merge.

arax closed this May 11, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment