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.

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

Code from swarm that could be moved to ocean #244

Open
3 of 4 tasks
gavin-norman-sociomantic opened this issue Jan 17, 2018 · 6 comments
Open
3 of 4 tasks

Code from swarm that could be moved to ocean #244

gavin-norman-sociomantic opened this issue Jan 17, 2018 · 6 comments

Comments

@gavin-norman-sociomantic
Copy link

gavin-norman-sociomantic commented Jan 17, 2018

Some code utilities have built up in swarm that might be a good fit for ocean.

Other things that were considered, but seemed too specialised:

@gavin-norman-sociomantic
Copy link
Author

FieldSizeSum would be an obvious candidate for ocean.meta.

@gavin-norman-sociomantic
Copy link
Author

TreeMap and TreeQueue could go in ocean.util.container.

@gavin-norman-sociomantic
Copy link
Author

StructPacker is generic, but I'm not sure whether any other apps need to serialize structs in memory in this way.

@gavin-norman-sociomantic
Copy link
Author

gavin-norman-sociomantic commented Jan 17, 2018

ByteCountHistogram (sociomantic-tsunami/ocean#441) and TimeHistogram could go in ocean.math.

@gavin-norman-sociomantic
Copy link
Author

gavin-norman-sociomantic commented Jan 17, 2018

AcquiredResources is generic, but I'm not sure whether any other apps would benefit from it. Possibly other servers where the resources used to handle different requests vary significantly.

@gavin-norman-sociomantic
Copy link
Author

The various bits of code that deal with hashes in swarm ought to be combined with similar code in ocean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant