Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

consider security/performance impact of ordered=1 serialization parameter #37

Open
peacekeeper opened this issue Apr 30, 2015 · 0 comments
Open

consider security/performance impact of ordered=1 serialization parameter #37

peacekeeper opened this issue Apr 30, 2015 · 0 comments
Assignees
@peacekeeper
Labels
performance security
Milestone
release-0.8

Comments

@peacekeeper
Copy link
Member

In various serialization formats, the ordered=1 parameter will output the serialized graph in an "ordered" form (according to some recommendations). This requires additional resources (time and memory).

Maybe support for this parameter should be disabled by default, as it is only useful for displaying a graph in a human-readable form.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@peacekeeper peacekeeper

Labels
performance security
Projects
None yet
Milestone
release-0.8
Development

No branches or pull requests
1 participant
@peacekeeper