Ticket #46 (closed enhancement: fixed)

Opened 2 years ago

Last modified 20 months ago

Event Loop/IO Channel integration

Reported by: scott Owned by: scott
Priority: major Milestone: Sagot 0.1
Component: Sagot Version:
Keywords: Cc:

Description

Integrate EventLoop? and IOChannel APIs

  • Allow multiple IOChannels and FileChannels? to be added to an event loop
  • All IO events must be operable before closing this item

Change History

Changed 2 years ago by scott

(In [24]) IOChannel Integration

  • Made first steps toward integrating IOChannel with the event framework
  • Added constants to IOChannel for watch types
    • IOChannel.READ for read-ready events
    • IOChannel.WRITE for write-ready events
    • IOChannel.READ_PRIORITY for read-now (buffer full type) high proprity events
    • IOChannel.ERROR for read/write error events
    • IOChannel.HANGUP for sig-hup and disconnect events
    • IOChannel.INVALID for other error types (closed filehandle, etc)
  • Added close method to IOChannel objects
  • Added watch method (currently non-functional)
  • Fixed error handling
    • undefined references to sagot_iochannel_error
    • sagot_iochannel_error and GError object dereferencing problems
  • Fixed read, readline, getc methods
    • Problem with return value assignments
    • Buffer lengths were using JSVAL_TO_DOUBLE which gives us poor behavior

Still lots of warnings at compile time

refs #45, #46

Changed 20 months ago by scott

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

This is currently working with GIOChannels through the FileChannel? interface as of [37].

Note: See TracTickets for help on using tickets.