Type | Wish | Status | submitted | Date | 7-Apr-2013 12:46 |
---|---|---|---|---|---|
Version | r3 master | Category | Ports | Submitted by | fork |
Platform | All | Severity | minor | Priority | normal |
Summary | Rename events like READ (when meant to pair w/WROTE) into SEEN, etc. |
---|---|
Description |
I got a bit confused looking at some event code on port schemes. Here is the list of events I later found: * lookup * connect * wrote * read * close * error * done I wouldn't have thought anything of it if wrote hadn't been in there. But because it was, I thought about how it seemed more literate than WRITE being the event name. It made me want to see more consistency. I know that READ ("red") is the past tense of READ ("reed")...and it is consistent in that sense. But it is pretty confusing, in a place that's confusing enough. REDDIT is probably trademarked, and it's weird looking anyway. So the best single short word I could think of was SEEN. Here's a potential list: * lookup => looked * connect => connected * write => wrote * read => seen * close => closed * error => failed * done => done If there's a transformation turning WRITE into WROTE somewhere, it seems it would be easy to apply to the other cases. I suppose the alternative suggestion would be to turn WROTE into WRITE for consistency. But I liked the literacy of it, after coping with a lot of onWrite or Event_WRITE_DONE in other systems. :-/ |
Example code |
Assigned to | n/a | Fixed in | - | Last Update | 7-Apr-2013 20:40 |
---|
Comments | |
---|---|
(0003803)
rgchris 7-Apr-2013 13:02 |
As the events are in process, would it be more appropriate to use present tense? — starting/initiating, connecting, writing, reading, closing, failing, finishing/completing |
(0003804)
BrianH 7-Apr-2013 20:40 |
Are they? I thought that the 'wrote and 'read events triggered after some data has been read or written. The overall process is ongoing, but the event triggers after a part of the process happens.
Are the other events triggered at the beginning of a step? Maybe they aren't all past tense. |
Date | User | Field | Action | Change |
---|---|---|---|---|
7-Apr-2013 20:40 | BrianH | Comment : 0003804 | Added | - |
7-Apr-2013 13:02 | rgchris | Comment : 0003803 | Added | - |
7-Apr-2013 12:47 | fork | Description | Modified | - |
7-Apr-2013 12:46 | fork | Ticket | Added | - |