Excerpt from a conversation I had at the workplace (exact details aren't provided for reasons of NDA):
System Architect: The frames are filtered into several different categories, each category having its own set of parameters which tell the device how to treat packets from that category. We then--
Me (Application Integration): Wait, what did you say they were filtered by?
SA: This parameter.
Me: But this parameter is one of the parameters in the category they are filtered TO...
SA: Yes.
Me: Well, if they're labeled by the initial filter as members of one category and then the category parameters label them a second time, we can have a situation where frames are labeled as members of a category which the very same category denies they are members of. We could also have a situation where frames are labeled as members of just one category, while three categories see them as members.
SA: I don't see a problem with that.
Me: ...
SA: Well, the user will simply have to be careful not to create such a situation.
Me: facedesks
In other news, I say this a lot (especially to myself), but I'm nearly done with bug-2169. It was somewhat challenging at several places, especially figuring Storable out (thanks
afuna!), but if nothing unexpected happens - right now it's just doing some writing (I almost wrote "finger work" but then thought better of it :) ), and cleaning up the code. So we should have (better) draft support soon, yay!
Up next is the HTTPs browsing bug. Though I might want to take a short hiatus with some minor bugs, because this last one has taken quite some work all in all, and the HTTPs one likely won't take any less.
System Architect: The frames are filtered into several different categories, each category having its own set of parameters which tell the device how to treat packets from that category. We then--
Me (Application Integration): Wait, what did you say they were filtered by?
SA: This parameter.
Me: But this parameter is one of the parameters in the category they are filtered TO...
SA: Yes.
Me: Well, if they're labeled by the initial filter as members of one category and then the category parameters label them a second time, we can have a situation where frames are labeled as members of a category which the very same category denies they are members of. We could also have a situation where frames are labeled as members of just one category, while three categories see them as members.
SA: I don't see a problem with that.
Me: ...
SA: Well, the user will simply have to be careful not to create such a situation.
Me: facedesks
In other news, I say this a lot (especially to myself), but I'm nearly done with bug-2169. It was somewhat challenging at several places, especially figuring Storable out (thanks
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Up next is the HTTPs browsing bug. Though I might want to take a short hiatus with some minor bugs, because this last one has taken quite some work all in all, and the HTTPs one likely won't take any less.