Ticket #31 (closed todo: invalid)

Opened 6 years ago

Last modified 3 years ago

Implement Async I/O

Reported by: coke Owned by: whiteknight
Priority: normal Milestone:
Component: core Version:
Severity: medium Keywords: io
Cc: Language:
Patch status: Platform:

Description


Change History

  Changed 6 years ago by allison

  • type changed from todo to feature

  Changed 6 years ago by coke

  • priority changed from normal to blocker
  • severity changed from medium to release

  Changed 6 years ago by Igor

Hi,

I've found a BSD licence library that could help for implementing Async I/O:

 http://monkey.org/~provos/libevent/

Sincerely,

Igor

  Changed 6 years ago by allison

  • component changed from none to core

  Changed 5 years ago by whiteknight

  • keywords io added
  • owner set to whiteknight
  • status changed from new to assigned
  • type changed from feature to todo

  Changed 5 years ago by allison

  • type changed from todo to roadmap
  • milestone changed from 2.0 to 2.6

  Changed 5 years ago by allison

  • priority changed from blocker to normal

  Changed 5 years ago by pmichaud

Rakudo might want to have async I/O available before 2.6, what blockers are there for this task? Is it design issues or implementation ones?

Pm

follow-up: ↓ 11   Changed 5 years ago by whiteknight

What I personally am waiting on right now is the completion of the Pipes implementation in the io_cleanups branch. The last few details are in Infinoid's head I think. So, we can get on his case about it, try to finish up pipes ourselves, or start on AIO without waiting for pipes, add them in afterwards.

Any of these is fine by me.

  Changed 4 years ago by allison

  • type changed from roadmap to todo
  • milestone 2.6 deleted

in reply to: ↑ 9   Changed 4 years ago by jkeenan

  • severity changed from release to medium

Replying to whiteknight:

What I personally am waiting on right now is the completion of the Pipes implementation in the io_cleanups branch.

We no longer have an io_cleanups branch in our repository.

Can anyone comment on where we stand with respect to the issues raised in this ticket?

Thank you very much.

kid51

  Changed 4 years ago by whiteknight

  • status changed from assigned to new

  Changed 3 years ago by jkeenan

Is this a ticket we should be keeping in our bug tracking system? Or is there a better way to handles issues that are "next generation Parrot"?

Thank you very much.

kid51

  Changed 3 years ago by whiteknight

  • status changed from new to closed
  • resolution set to invalid

this is an aimless todo which doesn't need to be in a ticket. We'll be doing AIO as part of the current threading work. I'm closing this ticket, we can track todo items and project goals in better places.

Note: See TracTickets for help on using tickets.