I can see technology like this being applied to reduce the amount of time engineers and others need to spend entering shape and texture data, hus letting them spend that time actually simulating product, leading to higher quality products.
Instead, the engineers will spend their time building more interesting lego robots rather than doing actual work:). I can see it now, all these 30 something engineers raiding their kid's lego sets just to get some more bits to build a better scanner....
To follow up the other posts here, yes RFC is a Request for comment. That is, as one who is authoring a number of them, you go through a whole draft stage (I've seen some in the double digit range of draft revisions) that get commented on. Then, at some stage that goes to be an experimental RFC. After more hacking (remember that running code rules in the world of the IETF) it may become informational or standard. At these stages the new RFC outdates the old RFC, again asking for more comments.
Rarely is a single RFC sufficient to generate a standard on. They are always updated by later ones. Even the old standards like Telnet has some thirty odd RFCs associated with it (last time I looked, including the April 1 variants).
Love the new arrangements, but there's one bit that has disappeared that I really loved. If anyone can tell me how to do this under the new arrangements please tell me!
Basically, I could to pick a particular thread with everything as threaded comments. If the thread looked interesting I would swap just that thread to flat mode and read the lot. Now, if I'm in a thread and then tell it to view in flat mode it moves the entire article + all replies to flat mode - dumping me out of the thread I was in and back to the original page. I can't just optionally see a thread flat (or nested for that matter either). Rob, I'd really like to see this put back in again please!
I dunno, but I once say an entire raytracer written in postscript. It was the most amazing hack I had ever seen. It took about 40 minutes for our (then) brand new HP laserJet 4M+ to produce this thing. I know it wasn't an EPS or other way because that was the time where I used to be able to read raw postscript and be able to interpret what was going on (had to write my own PS output for a graphics program for work stuff....)
If they can write a ray tracer in PS I'm pretty sure that somebody must have hacked a network driver with the stuff somewhere....
To answer your first point, I imagine this wouldn't be that hard to do. IPP is based on HTTP, which means that with HTTP/1.1 keepAlives you can have a dialog with the printer. I'd imagine a conversation along the lines of
Server: 302 Redirect, Location of Postscript printer is: URL1, Location of Win32DIB printer is: URL2
Client: OK thanks, close()
Client: follows redirect Client: connect(), keepAlive = true HTTP/1.1 PUT Content-Type: application/win32DIB (data follows here
And that's it. Just by using the facilities of HTTP servers and the protocol you should get automatic language selection based on what you have. Redirects probably would be the best way to then send it to the printer that supports both your requirements and the internal driver requirements.
As I understand it (I know lots about HTTP and networking, and enough to be dangerous with JINI), the two couldn't work together nicely without a lot of extra work.
The main cause for the difference is that JINI relies on RMI to do the dirty work of communications. RMI is based on Sockets, so are HTTP connections. Both of them form at least some layer of abstraction that are totally different. For example, to use HTTP in a Java application normally you just do this
java.net.URL url = new URL("http://www.vlc.com.au/"); Object contents = url.getContents();
Now on the JINI side, you do a lot of different things (too much code to explain here). You can't simply layer the HTML over the top of the JINI calls.
Now, stuff that I'm playing with for the IETF, can do this sort of stuff. URNs are a sibling to URLs but without the location and protocol specific parts. So, it is technically possible to name a printer eg:
urn:kinkos:somestore_id/the_colour_lazer/2
Ask for a connection to it and then pass the document down it. Underneath all of this JINI would find the printer for you and then IPP would pass the document to the printer. Having seem this IPP stuff come back into my radar I'm really tempted to hack this together over the top of my existing URN java libs. Also, a JINI resolver is on the way soon so I reckon given a couple of months I could have this whole shebang working for ya!
Darn, 403'd... Then there's an error that says that the error document also has forbidden access too! DOH! Methinks someone is modifying the server on the fly in response to the/. tidal wave hitting it at the moment.....
I think that's because Windows doesn't like to use the CPU. Instead it spends all its time swapping out to disk. Due to the large cache-miss percentage, the CPU gets time to cool down every 10 cycles or so while waiting for the HD to catch up.
Linux, OTOH, is so efficient that it keeps the CPU running all the time causing it to overhead. Either that or it spends all its time in interrupt handling routines.
I guess he hasn't read the GPL... you can't just start making a proprietary version of free software.
It also seems that you don't understand how licensing and copyright works. If I write the code I may license it however I like. In fact, I may have the same piece of code with two different licenses on it. In fact I do - I distribute my public code with the LGPL, and the stuff that the Australian Defence Forces use, have a different license on it. I own that code that I wrote and therefore may do whatever I like with it.
Ousterhout wrote the TCL code originally, so long as he sells a proprietry version of the code that does not include any improvements made by others then there is no problems legally.
Now, improvements made by others only is defined as the files where his copyright is on the top. If someone makes a (say) 2 line mod to a single file, but does not include their (c) symbol in the code as well, then they don't have a legal leg to stand on. The original (c) holder may take that code, put a different license on it and distribute it commercially/proprietry if they wish. If someone wants to enforce that you (being the original code writer) don't redistribute their changes, you need to put your little (c) mark on it as well. If you don't there's no point in crying over spilt milk.
Advanced Imaging API from Sun/Javasoft. JAIA EA1 and EA2 had read-only support, but write support is coming in the next release, I believe
We tried using JAI, and frankly it sucks. It still uses Sun's image loading classes that consume 4 times the amount of memory that the image should take. It is very slow and major repaint problems. That's why we wrote our own. Now, in my code there somewhere, I think I put the encoders too. It supports JPEG and PNG and we had TIFF/BMP underway. I'll check. If it doesn't include the writers, ping me and I'll send you the code.
If you want it, I've got a whole swag of library code to handle it. It works as content handlers in Java so pointing a URL at it, you will get a BufferedImage back (or Image if you need 1.1 spt). The only difference here is that you can't use it with Toolkit.getImage() | createImage()
>No one pretended to be clever in the movie, which was refreshing
Ah good to hear! Things like movies usually take a long time to make it into this part of the world (unless its the blockbuster type movies, in which case it usually is about 4-6 weeks post USA release).
Down under here, a couple of years ago, some guys got done for exactly this. IIRC it was the Commonwealth Bank (Which Bank?). Basically all they did was to siphon the partial cents from each interest calculation of every account into their own separate account. Doesn't sound like much, but when you work out that every day there are a couple of million accounts that their doing this to, it suddenly adds up to very large sums of spare cash.
As both a programmer and a writer I can see both sides of the story here. To all the kiddies out there that think being a "hacker" is the one true thing and that writers like Katz are just a bunch of windbag looser, you've got a lot to learn in life.
As another moderately successful writer (yes, here I am at work finishing off the contribution to my latest book - on Java3D), I can honestly say that writing is a sh*tload more difficult than coding. In coding, so long as you're APIs work as documented, it doesn't matter what happens inside. You get the work done, and somebody keeps employing you. As a writer, if you cannot explain yourself clearly your book won't sell, and no publisher is going to ask you to do another - no food on the table. It's easy to be a mediocre coder and live. It's not easy to be a mediocre writer and live.
Before you all just start another flame fest in my direction, how about you go and have a look at my homepage and resume. I've produced more than half a million lines of GPL/LGPL'd code in my lifetime, 8 books as well as a lot of ISO spec work. I think I might be just qualified enough to comment. (oops darn, some of the links are broken on the web pages, try a CLI FTP)
BTW - I don't know what everyone else got as a fortune on the page, but I thought this was rather appropriate:
Love your enemies: they'll go crazy trying to figure out what you're up to.
Slashdot Mirror
Instead, the engineers will spend their time building more interesting lego robots rather than doing actual work :). I can see it now, all these 30 something engineers raiding their kid's lego sets just to get some more bits to build a better scanner....
To follow up the other posts here, yes RFC is a Request for comment. That is, as one who is authoring a number of them, you go through a whole draft stage (I've seen some in the double digit range of draft revisions) that get commented on. Then, at some stage that goes to be an experimental RFC. After more hacking (remember that running code rules in the world of the IETF) it may become informational or standard. At these stages the new RFC outdates the old RFC, again asking for more comments.
Rarely is a single RFC sufficient to generate a standard on. They are always updated by later ones. Even the old standards like Telnet has some thirty odd RFCs associated with it (last time I looked, including the April 1 variants).
Basically, I could to pick a particular thread with everything as threaded comments. If the thread looked interesting I would swap just that thread to flat mode and read the lot. Now, if I'm in a thread and then tell it to view in flat mode it moves the entire article + all replies to flat mode - dumping me out of the thread I was in and back to the original page. I can't just optionally see a thread flat (or nested for that matter either). Rob, I'd really like to see this put back in again please!
If they can write a ray tracer in PS I'm pretty sure that somebody must have hacked a network driver with the stuff somewhere....
Client: connect(),
keepAlive = true;
Accept: Postscript/1.0,Win32DIB
Server: 302 Redirect, Location of Postscript printer is: URL1, Location of Win32DIB printer is: URL2
Client: OK thanks, close()
Client: follows redirect
Client: connect(), keepAlive = true
HTTP/1.1 PUT Content-Type: application/win32DIB (data follows here
And that's it. Just by using the facilities of HTTP servers and the protocol you should get automatic language selection based on what you have. Redirects probably would be the best way to then send it to the printer that supports both your requirements and the internal driver requirements.
The main cause for the difference is that JINI relies on RMI to do the dirty work of communications. RMI is based on Sockets, so are HTTP connections. Both of them form at least some layer of abstraction that are totally different. For example, to use HTTP in a Java application normally you just do this
java.net.URL url = new URL("http://www.vlc.com.au/");
Object contents = url.getContents();
Now on the JINI side, you do a lot of different things (too much code to explain here). You can't simply layer the HTML over the top of the JINI calls.
Now, stuff that I'm playing with for the IETF, can do this sort of stuff. URNs are a sibling to URLs but without the location and protocol specific parts. So, it is technically possible to name a printer eg:
urn:kinkos:somestore_id/the_colour_lazer/2
Ask for a connection to it and then pass the document down it. Underneath all of this JINI would find the printer for you and then IPP would pass the document to the printer. Having seem this IPP stuff come back into my radar I'm really tempted to hack this together over the top of my existing URN java libs. Also, a JINI resolver is on the way soon so I reckon given a couple of months I could have this whole shebang working for ya!
Darn, 403'd... Then there's an error that says that the error document also has forbidden access too! DOH! Methinks someone is modifying the server on the fly in response to the /. tidal wave hitting it at the moment.....
Linux, OTOH, is so efficient that it keeps the CPU running all the time causing it to overhead. Either that or it spends all its time in interrupt handling routines.
Maybe I'm just making this all up :P
self: *THWACK*
[esc]ZZ
depending on whether you are editing text or not, it is either 2 or 3 keystrokes.....
It also seems that you don't understand how licensing and copyright works. If I write the code I may license it however I like. In fact, I may have the same piece of code with two different licenses on it. In fact I do - I distribute my public code with the LGPL, and the stuff that the Australian Defence Forces use, have a different license on it. I own that code that I wrote and therefore may do whatever I like with it.
Ousterhout wrote the TCL code originally, so long as he sells a proprietry version of the code that does not include any improvements made by others then there is no problems legally.
Now, improvements made by others only is defined as the files where his copyright is on the top. If someone makes a (say) 2 line mod to a single file, but does not include their (c) symbol in the code as well, then they don't have a legal leg to stand on. The original (c) holder may take that code, put a different license on it and distribute it commercially/proprietry if they wish. If someone wants to enforce that you (being the original code writer) don't redistribute their changes, you need to put your little (c) mark on it as well. If you don't there's no point in crying over spilt milk.
We tried using JAI, and frankly it sucks. It still uses Sun's image loading classes that consume 4 times the amount of memory that the image should take. It is very slow and major repaint problems. That's why we wrote our own. Now, in my code there somewhere, I think I put the encoders too. It supports JPEG and PNG and we had TIFF/BMP underway. I'll check. If it doesn't include the writers, ping me and I'll send you the code.
http://www.vlc.com.au/~justin/java/image s/ .9.zip
ftp://ftp.vlc.com.au/pub/imageloader_0
Basically, the list of supported formats are:
- TIFF
- JPEG
- BMP
- XPM/XBM
- PNG (1.0, not 1.1 yet)
- GIF (but wrapper around standard java impl)
- TGA
All the code is LGPL'd except where the back end libraries have different licenses as provided by their authors.The code has been tested under Solaris, HP-UX and Win32 (precompile bins for Win32 only).
was refreshing
Ah good to hear! Things like movies usually take a long time to make it into this part of the world (unless its the blockbuster type movies, in which case it usually is about 4-6 weeks post USA release).
Down under here, a couple of years ago, some guys got done for exactly this. IIRC it was the Commonwealth Bank (Which Bank?). Basically all they did was to siphon the partial cents from each interest calculation of every account into their own separate account. Doesn't sound like much, but when you work out that every day there are a couple of million accounts that their doing this to, it suddenly adds up to very large sums of spare cash.
As another moderately successful writer (yes, here I am at work finishing off the contribution to my latest book - on Java3D), I can honestly say that writing is a sh*tload more difficult than coding. In coding, so long as you're APIs work as documented, it doesn't matter what happens inside. You get the work done, and somebody keeps employing you. As a writer, if you cannot explain yourself clearly your book won't sell, and no publisher is going to ask you to do another - no food on the table. It's easy to be a mediocre coder and live. It's not easy to be a mediocre writer and live.
Before you all just start another flame fest in my direction, how about you go and have a look at my homepage and resume. I've produced more than half a million lines of GPL/LGPL'd code in my lifetime, 8 books as well as a lot of ISO spec work. I think I might be just qualified enough to comment. (oops darn, some of the links are broken on the web pages, try a CLI FTP)
BTW - I don't know what everyone else got as a fortune on the page, but I thought this was rather appropriate:
So will you embrace and extend this?