It would seem that the law is so confusingly vague that it doesn't apply to things like VPN and NAT. In a NAT process, packets are wrapped with a new origination address, so that a response can be properly routed and received. One valid argument is that there is no concealment -- the packet is coming from the routed/NAT device, and it says it is!. The fact that the content of the packet is from somewhere else doesn't really seem to matter, under this view.
Whether that is an argument that the Michagan AG would accept, is another question. But, without valid source and destination addresses, the packets are just not going to be useful on the network.
This law seems to apply much better to spam with forged and/or altered headers, in which the actual source address is not easily recoverable from the message.
The EFF has posted a pdf of the injunction at their site, for viewing. There does not seem to be any commentary, much less any positioning, on this particular case by the EFF(yet).
I would hope that, if they do become involved, they will agree on the side of the recent FatWallet case, in which posted price information was decided not copyrightable.
It's really not fair to say people are involved merely because they are posting information for public benefit.
Why they don't call it a "lens" is beyond me.
It seems to have to components: an incoming collector area, which focuses signals on the receptor; and an outgoing dispersive area, which spreads the outbound signal to cover a broad region.
Look guys, the question was about application architecture, not about GUI design, button layout, color schemes, etc. So, in that vein...
You mention MVC. This is a very useful abstraction, but you're right in saying that it doesn't address the larger question of application architecture. One kind of global abstraction that seems to help for large interfaces is some kind of messaging system. For example, you can use a global queue of update events (sent by Models when things change) which all interested Views can lsiten to, and react accordingly.
Some real problems come when you want views to react to changes so some other view (but NOT the underlying model data). e.g. changing from 2d to 3d display, you might want various menus to appear, disappear, or have entires change/gray-out. This breaks down the MVC abstraction to varying degrees.
At the end of it all, I also haven't seen much in the literature on architectures for large GUI apps. I think this is because very few of them are really ever produced. Most apps you see are, at the base of it all, fairly simple, and require only one or two views with pretty straightforward control architecture.
I read a lot here about he intrinsic beauty and logic of math. Personally, I agree -- but then, I already understand a lot of it.
I think that for young students, a good connection with the real world is a requirement for coming to an understanding of the math.
I've taught CS at the graduate level, and was always utterly disappointed in the degree of math understanding of the average student. My wife researches grade school math education, is us utterly disappointed with the manner in which it's taught.
Algebra isn't that hard, really. I like to claim that any sixth grader who can figure out what he can get for lunch with the money in his packet has a basic grasp of it already. Part of the problem is that students are encouraged, from a very early age, to believe that they won't really understand math. "Just do it this way", and you'll get the right answer. They aren't usually taught why that way works, or what's going on. They just push numbers around the right way, and write down what you get.
There's a definite lack of connection between the "real world" that the students live in and the way it gets talked about in math class.
I also agree that there's far too much repitition in the math curriculum. From my own experience, we learned "fractions" in third grade, did them again in 4th, reviewed them in 5th, went back to them in 6th, etc. By this time I had already dropped out, and started doing algebra and trig as a way to keep myself occupied. Many other students just stopped paying attention, not because it was hard or they didn't get it, but because it was clear that it wasn't ever going anywhere. What a sham!
The poster makes some really bizarre complaints against other languages:
any script based language (Matlab, Numeric Python, Scilab) to be inadequate as soon as it is necessary to use loops to describe a problem and using such tools for recursive systems can be a real pain.
These are exactly the places where these languages excel, especially as compared with fortran!
Fortran has only the most basic looping structures, and the lack of complex structures, pointers, and object abstraction makes writing any complex algorithm an excercise in mental anguish.
Things like Numerical Python were implemented specifically to put the control structures in a language that is readable, writable, portable and understandable. If you really need to, you can code the bit twiddling in C and link from Python/Matlab/whatever, but for god's sake, leave the high-level program structure up where you can read it.
Many of these comments are missing the point. The paper is not really about categorizing your email.
The main result in Kleinberg's paper relates to finding NEW topics that start to appear in the stream. Let's say you already have categorization filters (procmail, keyword filters, your own set of folder hierarchies, whatever...), but there's a new topic that starts showing up in your mail, or in your newsgroup feed, or on CNN. Klienberg's result is a way to find that the new stuff really is NEW, and you might want to group it up together, and make a folder for it. You could do that automatically, or by hand, but first you have to know that there's a topic.
Slashdot Mirror
Whether that is an argument that the Michagan AG would accept, is another question. But, without valid source and destination addresses, the packets are just not going to be useful on the network.
This law seems to apply much better to spam with forged and/or altered headers, in which the actual source address is not easily recoverable from the message.
I would hope that, if they do become involved, they will agree on the side of the recent FatWallet case, in which posted price information was decided not copyrightable.
It's really not fair to say people are involved merely because they are posting information for public benefit.
Why they don't call it a "lens" is beyond me. It seems to have to components: an incoming collector area, which focuses signals on the receptor; and an outgoing dispersive area, which spreads the outbound signal to cover a broad region.
--tsw
You mention MVC. This is a very useful abstraction, but you're right in saying that it doesn't address the larger question of application architecture. One kind of global abstraction that seems to help for large interfaces is some kind of messaging system. For example, you can use a global queue of update events (sent by Models when things change) which all interested Views can lsiten to, and react accordingly.
Some real problems come when you want views to react to changes so some other view (but NOT the underlying model data). e.g. changing from 2d to 3d display, you might want various menus to appear, disappear, or have entires change/gray-out. This breaks down the MVC abstraction to varying degrees.
At the end of it all, I also haven't seen much in the literature on architectures for large GUI apps. I think this is because very few of them are really ever produced. Most apps you see are, at the base of it all, fairly simple, and require only one or two views with pretty straightforward control architecture.
I think that for young students, a good connection with the real world is a requirement for coming to an understanding of the math. I've taught CS at the graduate level, and was always utterly disappointed in the degree of math understanding of the average student. My wife researches grade school math education, is us utterly disappointed with the manner in which it's taught.
Algebra isn't that hard, really. I like to claim that any sixth grader who can figure out what he can get for lunch with the money in his packet has a basic grasp of it already. Part of the problem is that students are encouraged, from a very early age, to believe that they won't really understand math. "Just do it this way", and you'll get the right answer. They aren't usually taught why that way works, or what's going on. They just push numbers around the right way, and write down what you get. There's a definite lack of connection between the "real world" that the students live in and the way it gets talked about in math class.
I also agree that there's far too much repitition in the math curriculum. From my own experience, we learned "fractions" in third grade, did them again in 4th, reviewed them in 5th, went back to them in 6th, etc. By this time I had already dropped out, and started doing algebra and trig as a way to keep myself occupied. Many other students just stopped paying attention, not because it was hard or they didn't get it, but because it was clear that it wasn't ever going anywhere. What a sham!
--tsw
any script based language (Matlab, Numeric Python, Scilab) to be inadequate as soon as it is necessary to use loops to describe a problem and using such tools for recursive systems can be a real pain.
These are exactly the places where these languages excel, especially as compared with fortran! Fortran has only the most basic looping structures, and the lack of complex structures, pointers, and object abstraction makes writing any complex algorithm an excercise in mental anguish.
Things like Numerical Python were implemented specifically to put the control structures in a language that is readable, writable, portable and understandable. If you really need to, you can code the bit twiddling in C and link from Python/Matlab/whatever, but for god's sake, leave the high-level program structure up where you can read it.
The main result in Kleinberg's paper relates to finding NEW topics that start to appear in the stream. Let's say you already have categorization filters (procmail, keyword filters, your own set of folder hierarchies, whatever...), but there's a new topic that starts showing up in your mail, or in your newsgroup feed, or on CNN. Klienberg's result is a way to find that the new stuff really is NEW, and you might want to group it up together, and make a folder for it. You could do that automatically, or by hand, but first you have to know that there's a topic.
there's a bunch of other work in this area, what the NLP types call TDT -- "Topic Detection and Tracking"