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

I/O, File, and Network API #28

Closed
11 tasks done
azjezz opened this issue Jul 9, 2020 · 3 comments · Fixed by #257
Closed
11 tasks done

I/O, File, and Network API #28

azjezz opened this issue Jul 9, 2020 · 3 comments · Fixed by #257
Assignees
@azjezz
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: In Progress This issue is being worked on, and has someone assigned. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
v1.0.0 v2.0.0
Milestone
2.0.0

Comments

@azjezz
Copy link
Owner

azjezz commented Jul 9, 2020 •
edited
Loading

@azjezz azjezz added Status: On Hold Similar to blocked, but is assigned to someone. May also be assigned to someone because of their exp Type: Enhancement Most issues will probably ask for additions or changes. labels Jul 9, 2020
@azjezz azjezz self-assigned this Jul 9, 2020
@azjezz azjezz changed the title I/O/File/Network API I/O, File, and Network API Jul 9, 2020
@azjezz azjezz added the Priority: High After critical issues are fixed, these should be dealt with before any further issues. label Jul 9, 2020
@azjezz azjezz added this to To do in v1.0.0 Jul 9, 2020
@azjezz azjezz added this to the v1.0.0 milestone Jul 12, 2020
@azjezz azjezz added Status: In Progress This issue is being worked on, and has someone assigned. and removed Status: On Hold Similar to blocked, but is assigned to someone. May also be assigned to someone because of their exp labels Sep 28, 2020
@azjezz azjezz modified the milestones: 0.1.0, 1.0.0 Oct 30, 2020
@HenkPoley
Copy link

HenkPoley commented Feb 17, 2021 •
edited
Loading

Accidentally stumbling onto this. Would the I/O addition allow one to keep read and write access more clearly separate? E.g. an API with a cache backing (cache reads) for speed, and in another part validation (database reads) as a first step, before writing out data. A bit akin to the Haskell I/O monad (which I am not very familiar with).

Of course with backing from Psalm, since PHP doesn't care.

@azjezz
Copy link
Owner Author

azjezz commented Feb 17, 2021

see #127

for now, we want to have basic IO handles, later add support for Files and Network ( Sockets, Servers .. etc )

@azjezz azjezz added this to To do in v2.0.0 Nov 4, 2021
@azjezz azjezz mentioned this issue Nov 6, 2021
Merged
@azjezz
Copy link
Owner Author

azjezz commented Nov 6, 2021

@HenkPoley FYI, File API has been implemented in #250, network/tcp/udp are in the work #257.

v2.0.0 automation moved this from To do to Done Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@azjezz azjezz

Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: In Progress This issue is being worked on, and has someone assigned. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
No open projects
v1.0.0
  
To do
v2.0.0
Done
Milestone
2.0.0
Development

Successfully merging a pull request may close this issue.

feat(network): introduce network, tcp, and unix components azjezz/psl
2 participants
@HenkPoley @azjezz