Github user aholmberg commented on the issue:
https://github.com/apache/tinkerpop/pull/448
> you changed GraphSONWriter and GraphSONWriter to GraphSONIO
This was not Python-specific, but felt like a natural design to me. I
unified the I/O per type, and tied those together at the top level in
`GraphSONIO`. It seems strange to me to have the two sides of the same encoding
split between classes. I thought I saw something in the java impl called
`GraphSONIO`, but maybe I was mistaken.
I can split them up, but then it means carrying around two things to
encode/decode everywhere, instead of one:
`connection = DriverConnection(..., graphson_reader=GraphSONReader(...),
graphson_writer=GraphSONWriter(...))`
vs.
`connection = DriverConnection(..., graphson_io=GraphSONIO(...))`
I'll study the Java impl. a little closer to see if I can understand the
benefit. Please let me know if you have any further thoughts.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
