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

text-based file source/sink #39

Open
guruofquality opened this issue Jun 23, 2016 · 1 comment
Open

text-based file source/sink #39

guruofquality opened this issue Jun 23, 2016 · 1 comment

Comments

@guruofquality
Copy link
Contributor

Create text-based file IO blocks that have configurable delineations.

@guruofquality
Copy link
Contributor Author

Created a text-file sink: 055a316

A matching file source is going to be harder for a few reasons:

  • there’s not string parsing for every type that has a toString() option
  • recovering the message type, or buffer type is not possible
  • this may mean manual specification for the data type and destination: message, stream, packet...

Currently, an entire port can be written to file and recovered by using: serializer -> binary file sink, and binary file source -> deserializer. So maybe since that use case is already covered, we dont need a text file source, or perhaps a very dumbed down source with only basic stream options.

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

No branches or pull requests

1 participant