Confirmed users
195
edits
(changed numbered list to bulleted) |
No edit summary |
||
| Line 5: | Line 5: | ||
Ideally, I would have expected these two be two interfaces. Because that's what they are, "Interfaces to two things, viz a connection and a transaction". But for some reason these were made abstract classes. Probably to avoid usage from JS. Then again these could be made non-scriptable interfaces. Now as you know, I seriously do not know why these are abstract classes and not interfaces. | Ideally, I would have expected these two be two interfaces. Because that's what they are, "Interfaces to two things, viz a connection and a transaction". But for some reason these were made abstract classes. Probably to avoid usage from JS. Then again these could be made non-scriptable interfaces. Now as you know, I seriously do not know why these are abstract classes and not interfaces. | ||
[When you say interface you mean IDL file? There's no point to write an IDL for these two interfaces really. They're only supposed to be used inside of the HTTP implementation, and there doesn't seem to be any advantage in being restricted by IDL syntax --[[User:Biesi|Biesi]] 06:20, 18 July 2008 (PDT)] | |||
Going ahead, there are multiple implementations of these two behavioral classes. Some of which I have come across are: | Going ahead, there are multiple implementations of these two behavioral classes. Some of which I have come across are: | ||