Within Efl_Core this Exe namespace should be moved out of Ecore
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T7142 efl 2.0 considerations | ||
| Open | cedric | T5301 Make EFL easier to use by improving its interface | ||
| Open | raster | T5522 EO: Ecore API | ||
| Open | • segfaultxavi | T6394 Refactor Ecore.Exe to EFL.Exe |
Comment Actions
whenever doing this, *PLEASE* use Efl.Io interfaces, so it's similar everywhere (ie: API will be mostly the same as the one for Efl.Net), namely Efl.Io.Reader, Efl.Io.Closer and the likes. For UNIX, you can benefit from Efl.Io.Reader.Fd and similar, not sure how is that on Windows.
With that, you only need the basics: monitor for incoming data and when writes can be done without blocking, as well as monitor child exit. Buffering and high level operations should be done by the existing Efl.Io.Copier and Efl.Io.BufferedStream
Comment Actions
@ajwillia.ms @zmike Can I have more information on the purpose of this task? As it is written now, I do not understand what needs to be done.
There currently exist efl_exe.eo and ecore_exe.eo classes but their relationship is not readily apparent.