Slashdot Mirror

Lemme see:

Full open source projects:

OpenOffice

Netbeans

Tomcat (The source was gifted from Sun)

NFS (gifted to the Linux community)

They also have source that free for research and internal use at:

http://www.sun.com/software/communitysource/index. html

They also have given financial and programming support to:

Gnome

Mozilla

And I'm just scratching the surface! And for the record, Lutris was perfectly able to create a fully open source, J2EE branded server. The catch 22 was that they couldn't open source Sun's code so they would have to write their own. Did they? No.

Geez, you people could at least TRY to understand the issue before shooting off at the mouth.

Disclaimer: This post does not meet established Slashdot doctrine. Go ahead, mod me down. I dare you. Be a censor just like the news media. The truth? You can't handle the truth!

Apache Projects have got to be some of the most collaborative and open projects out there. Go read
the Apache Jakarta's Getting Involved document to see how to get involved there. It's the same for all Apache projects.

If you are looking for documentation in implementing C/C++ or Java and XML. We are using the Xerces parser at xml.apache.org. It has documentation on Sax, Sax2, and DOM.

That all depends on exactly why you are doing this. If you are doing this just to get practice on building a basic parser, then you probably want to look at some basic compiler books, or the documentation on the common lexical and parser generators (i.e. Flex and Bison). While that may be useful, remember that correct XML requires a little more work than just parsing (opening and closing tag names must match exactly, etc.). You probably want to read the w3c recommendation, or some annotated version if it.

Alternatively, if you just want to be able to read in XML, there are several free or GPL libraries out there already. The one I'm most familiar with is Xerces, the xml parser for the apache project. You can find it here.

If you are not a CS student, you probably want to make sure you're familiar with some of the basics (a set of languages, basic data structures, etc.) before taking on this sort of project. I'd recommend C++ and its Standard Template Library, but there are many other viable alternatives out there (e.g. C, Python, Java, etc.). There are lots of books which cover this, though none come to mind offhand. If any other reader would like to help, I'd be much obliged.

I hope some of this info helps, and I wish you luck.

Isn't this part of the idea behind the Apache Struts project? It seems like a great idea, although I haven't yet developed anything using the framework. Still the servlet/service mapping process looked pretty easy to do since it was all in XML.

I'm also a big fan of XML. I have been pulling XML from a variety of news sites (including Slashdot) for display on my own site. I just built a Java class which gets run every 30 minutes and pulls the latest headlines and then rendering is all done with XSL. The XSL was a pain to generate since there are all sorts of different implementations of the RSS/RDF frameworks, but once you figure it out it isn't too bad. In the end I had about 4 different XSL files for the 14 feeds I pull. The benefit is that once you have the basic XSL framework it is relatively easy to tweak it to appear different. If you build in CSS support you can even change the look and feel by modifying the CSS and not the XSL. Plus, if you use JRun it has a built in XSLT taglib for doing the conversion (although it is only about 3 lines using Xerces/Xalan). Too bad my site is down right now since my site (DSL) re-initialized my IP and I don't know what it is.

I also found the XML Pocket Reference book pretty handy to have around (although a bit slim on explanations).

Also, anyone know what is up with the slashdot.xml file? It doesn't seem to be updating as often lately. I thought this was automated in the code. Am I wrong?

-JFS

1. Sierra puts out (& have put out) a bunch of stuff that involve creative thought. 'The Secret Island of Dr. Brain', 'The incredible machine'(!), plus the others already mentioned.
2. Turn them on to html. Buy any old HTML 4 book w/CD. Use the CD repeatedly. Linux books w/CD usually have an Apache site already set up with the Caldera and Red Hat versions. Building a web site is relatively simple and can give them a chance to strut their stuff, literally. If you are running MicroSoft, the web site software (Option pack 4) is FREE, at you-know-where. If you are using Unix/Linux, the Apache web server software is FREE, too. So is the java stuff at Sun for javaServerPages (JSP). (Free there, too.) Allaire/Macromedia has a FREE JavaServerPages server (with no expiration date for a developer version) at . Have fun!

[A] lot of people wondered what role Apache will play in a future that might be dominated by .Net.

Not I, because I am aware that the Apache Software Foundation has been working on SOAP for sometime. Besides, Microsoft cannot dominate the future because, in the future, interoperability between systems will require open standards and open protocols that are not determined by a single corporation or business interest.

Does this answer some of your concerns about Apache's future?

Not at all. I am not concerned about Apache's future. I know that it will continue to thrive. Apache 2.0 has been in beta since March and will probably soon be released. Other Apache projects also kick butt, e.g., Tomcat 4.0, whose release is also imminent.

The NetHesive product seems primarily a savior for legacy applications, not the Apache web server.

[A] lot of people wondered what role Apache will play in a future that might be dominated by .Net.

Not I, because I am aware that the Apache Software Foundation has been working on SOAP for sometime. Besides, Microsoft cannot dominate the future because, in the future, interoperability between systems will require open standards and open protocols that are not determined by a single corporation or business interest.

Does this answer some of your concerns about Apache's future?

Not at all. I am not concerned about Apache's future. I know that it will continue to thrive. Apache 2.0 has been in beta since March and will probably soon be released. Other Apache projects also kick butt, e.g., Tomcat 4.0, whose release is also imminent.

The NetHesive product seems primarily a savior for legacy applications, not the Apache web server.

How do you think Torvalds created the linux kernel?

What is used/needed to develop on apache?

How did CmdrTaco make Slash?

What development tools do you need for mozilla

Impossible without GUI? Yeah, right. End of discussion.

I developed a system like this for a previous job. We started with a source browser and then began checking engineering documents into our repository and (thus) making them browsable on the web

It can be really be nice. The hardest things were social issues; it requires a bit more discipline to maintain documents in a repository than by file sharing and email. Establishing the taxonomy so that people know where to put things and where to look for them is critical; but getting a good search engine up[1] can help there. Using small documents to redirect browsers to the "right" place can also help, since you can take a document that spans categories and put it in multiple places. I also wanted to get a Wiki in place, but left before we got there.

Having the revisions of design docs and test specs (which always change as implementation proceeds) tied to the appropriate revs of the software and other documentation using CVS tags, perforce change #'s/labels, or whatever is really nice.

As far as linking, HTML and MSOffice links were always made relative to the current document, so you could browse them when you'd checked them out on to your local machine. That was another social issue: educationing people to be careful, since most HTML editors and MSOffice HTML manglers of that vintage needed a little extra care to create relative links.

Since this was software engineering, we also implemented in-browser diffs (a lot like CVS web) and source code browsing as research tools. Having the design and discovery ("hey! so that's how this code works!" "Quick write it down before you forget!") docs that can link to the source code means that a new team member can read through a design doc and jump in and see the source code (where we kept implementation documentation).

You can modify your server-side source code browser to find things like file:../../design/index.xml in source files and convert them http: links when browsed, then use an editor or xterm that activates embedded links and be able to refer to design docs in soruce code. This also allow developers to link out to web sites, though we slurped anything that important in to the repo to protect against bit rot.

Since you've choosen XML a priori, you should definitely look at AxKit (Perl-based) or Cocoon (if Java's your fave) as delivery vehicles. Both are ASF official projects, though AxKit is a recent addition and hasn't made it to an Apache webserver.

Never used Cocoon, but AxKit can easily back-end to CVS and apply whatever transformations you like. AxKit can apply it's own XPathScript and XSP (language="perl") style sheets; various C-based XSLT engines (Sablotron and libxslt come to mind); and, of course, 100% Pure Perl to thoroughly munge your docs. Then it caches the results (if you like) and optionally GZips them (which is nice for dial-up or VPN use).

AxKit's main drawback at the moment is that it's web site is down due to sluggishness of British Telecom in installing a new data line, but you can find out more by searching cpan for the AxKit module.

If you do it right, you will have a very cool system.

HTH,

Barrie

[1] We did this before XML was all the rage, and getting meaningful searches of MSOffice files checked in to a reposiroty was a right pain. We ended up sharing out a directory tree that was updated nightly with the head revisions and letting people search with MSOffice's built in File Find.

I've been working on a project to document software engineering methodology and best practices (eventually to be published and freely available). The content is written in XML. I wrote the DTDs for the basic document types and XSL stylesheets for output to HTML. I've written a few docs already for the system (two, three dozen or more). Some notes on my experience.

1) Editing: I find the XML editors available online to be slow to use. I don't want to click on a tree to navigate through my document--too much mouse work--and I find the format for editing individual nodes is cumbersome if you have a complex document structure. I settled on using a good text editor (EditPlus, not free) with some templates for automatically inserting large node sections that are typically edited in a block. The editor has syntax-highlighting so it's easy to differentiate the XML from the content. I also have template files for quickly starting a new document of each type, with all the basic nodes already pasted within so I can open a new template and start typing.

2) Display: I wrote some simple XSL sheets to start with, that just displayed the XML in a readable, basic HTML format. I have my editor linked to a script that transforms the current XML on command, and opens the HTML in the same editor--so I can quickly preview the results. I use the Apache Xalan XSL processor with Java JDK 1.3. I also have an Apache/Jakarta Ant script to transform all documents on comment. Since I started, I have spent some time improving the layout, but writing a basic XSL for display is not difficult--I recommend having basic ones around (no gifs, simple tables, etc.) for no-nonsense preview of the content.

3) Navigation: I have specific tags in my docs (like reference or ext-reference for linking documents. The XSL generates the appropriate tag for navigation, based on attributes in the tag. My newer approach is to generate either static links or a link to a Java servlet with the page name; the servlet then handles the navigation request. The servlet approach has the advantage that it can eventually transform documents on the fly, allow you to specify a transformation type (e.g. pretty, simple, text-only) and even to pull content from a repository.

4) Content management: Right now I use directories to manage the content, since I support 5 document types, and use the file names to distinguish the content. I spent a bunch of time when I started figuring out the DTDs of the various document types so I would organize content most efficiently and with little or no duplication of intent. I recommend that approach--it's been a lot easier, when I want to write, to identify the document type I want, open a template, and start typing. I think this is where the first real effort comes, not in picking an editor, etc., but in deciding exactly how the information will be categorized. It's important to have searchable content, or content you need to introspect, to be pulled out from the main. For example, in using a reference tag, I can write a verification routine that checks the reference is valid (e.g. if a file, check that the file exists). I try to avoid writing anything I would need to parse out--for example, dumping a code sample write within a text block. I'd rather have a code-sample tag for easy identification.

I'd stress that the biggest hassle has been getting the XSL to work properly and generate readable XML, especially for more involved document structures. It's easy to break and hard to debug! In that vein, I recommend starting with very simple XSLs that output really really simple HTML and building up from there.

-Pdoubleya

I've been working on a project to document software engineering methodology and best practices (eventually to be published and freely available). The content is written in XML. I wrote the DTDs for the basic document types and XSL stylesheets for output to HTML. I've written a few docs already for the system (two, three dozen or more). Some notes on my experience.

1) Editing: I find the XML editors available online to be slow to use. I don't want to click on a tree to navigate through my document--too much mouse work--and I find the format for editing individual nodes is cumbersome if you have a complex document structure. I settled on using a good text editor (EditPlus, not free) with some templates for automatically inserting large node sections that are typically edited in a block. The editor has syntax-highlighting so it's easy to differentiate the XML from the content. I also have template files for quickly starting a new document of each type, with all the basic nodes already pasted within so I can open a new template and start typing.

2) Display: I wrote some simple XSL sheets to start with, that just displayed the XML in a readable, basic HTML format. I have my editor linked to a script that transforms the current XML on command, and opens the HTML in the same editor--so I can quickly preview the results. I use the Apache Xalan XSL processor with Java JDK 1.3. I also have an Apache/Jakarta Ant script to transform all documents on comment. Since I started, I have spent some time improving the layout, but writing a basic XSL for display is not difficult--I recommend having basic ones around (no gifs, simple tables, etc.) for no-nonsense preview of the content.

3) Navigation: I have specific tags in my docs (like reference or ext-reference for linking documents. The XSL generates the appropriate tag for navigation, based on attributes in the tag. My newer approach is to generate either static links or a link to a Java servlet with the page name; the servlet then handles the navigation request. The servlet approach has the advantage that it can eventually transform documents on the fly, allow you to specify a transformation type (e.g. pretty, simple, text-only) and even to pull content from a repository.

4) Content management: Right now I use directories to manage the content, since I support 5 document types, and use the file names to distinguish the content. I spent a bunch of time when I started figuring out the DTDs of the various document types so I would organize content most efficiently and with little or no duplication of intent. I recommend that approach--it's been a lot easier, when I want to write, to identify the document type I want, open a template, and start typing. I think this is where the first real effort comes, not in picking an editor, etc., but in deciding exactly how the information will be categorized. It's important to have searchable content, or content you need to introspect, to be pulled out from the main. For example, in using a reference tag, I can write a verification routine that checks the reference is valid (e.g. if a file, check that the file exists). I try to avoid writing anything I would need to parse out--for example, dumping a code sample write within a text block. I'd rather have a code-sample tag for easy identification.

I'd stress that the biggest hassle has been getting the XSL to work properly and generate readable XML, especially for more involved document structures. It's easy to break and hard to debug! In that vein, I recommend starting with very simple XSLs that output really really simple HTML and building up from there.

-Pdoubleya

I use stylebook for internal documents at planetu.com, but stylebook seems to be dead. Docbook is a much better choice. I just have not got around to converting to it.

The really nice thing about using XML is that I can automate some of the documents. Such as the list of valid form fields for a HTML/jsp page.

For the nightly builds, change logs and javadocs, I use Alexandria.

Check out SVG in Cocoon 2 which uses Batik for generating SVG graphics. Cocoon2 is an XML/XSLT framework.

I don't agree that the SVG viewer is flaky: the implementation is proprietary, but SVG itself is an open standard and this free software lets one "View Source" which alone far surpasses Flash: the "View Source" aspect of HTML is in large part responsible for its success as a language authored effectively by a large number of people.

The Adobe Viewer is only one of many ways to enjoy SVG. The Batik project is a fantastic Open Source implementation.

There is a Mozilla build by Alex Fritze that facilitates inline SVG (something that the Adobe Viewer is just starting to support in IE). That is an example of a "single current browser supporting SVG natively"... of course it's not yet in the main Mozilla build.

But SVG is not just for browsers: it can run in applications and on the server. It is far more than just a replacement for Flash...

Max

Browsing SVG

The only browser plug-in for SVG right now is Adobe's, and it only works in NS4 and IE5 for Mac and Win32. However, there is a rapidly-developing Win32 SVG-savy branch of Moz by Alex Fritz. No text support yet, alas, but the author suggests that it should be easy to port to other platforms.

Generating SVG

Sodipodi is a Win/Linux vector graphics program with SVG at its heart -- well worth a look. Sketch runs in Python and includes SVG in its import/export set. I've had good luck transforming complex Illustrator diagrams into SVG using Sketch.

On the Win platform, I'm quite fond of Jasc WebDraw; it's in beta and a fully functional demo is provided.

Finally, the versitility of the Batiklibrary is staggering. Written in Java, it includes a viewer, transcoders to png and jpg and a very cool Graphics2D implementation. The latter allows anything graphics that can be drawn to a java G2D panel to be instead output as SVG. This is a great way to get font dimension info for precision layout of SVG, as we've done building dynamic timelines at the Historical Event Markup Project.

But still - face it: Open source and free software is hobbyists writing code for their own well-being, because they (we) think it's fun, and/or because we need the software, and feels good about letting other people use and change said software too.

A quick glance at the Membership List of the Apache Software Foundation shows that there are about 63 members of which about 40 represent one company or the other. The same can be said of most of the other major Open Source projects from Mozilla to Linux to Perl. Corporations are beginning to see the benefits of Open Source software and are contributing both a lot more developer resources than anyone would have believed possible just a few years ago.

However, the fact that OS X has apache server built in makes it very desirable.

Apache HTTP Server is also available for Win32 machines (9x/me, nt/2k/xp). Here's a direct link to the Win32 binary/source distro (win95 needs Winsock 2; nt4, 95, and 98 need Windows Installer for nt or 9x). It's good for web development on machines that also have to run Office (say for students who can't afford to own several machines) and also good for file sharing.

Wrong. Apache is an enterprise-level product that is priced accordingly.

VMware GSX Server is an absolute must for any company looking to maintain multiple centralized development environments.

Wrong again. Removing MS Windows from all workstations is an absolute must for any company looking to maintain a decent development environment. Note change in wording: if the environment is centralized and multiple, you only have to maitain the "center" (server), and leaf node configuration is straightforward, right ?

How about the enormous chunk of Linux webservers? Last I read, Linux has supported IPv6 for some time now.

Yes, but does your cable or DSL provider route IPv6 ? Do they help you get your own /48 routed to your home if you want it ? I wish my cable provider supported IPv6 and/or multicast.

And your Linux webserver might have a bit of a problem serving IPv6 clients out of the tarball. Apache 1.3.x still needs a set of patches (available from the kame ftp server). Apache 2.0, still in beta supports it now.

the location bar becomes full length below the navigation buttons, and rectangular navigation buttons are used to save vertical space

If you care enough about it, write a chrome with this configuration.

that annoying "Search Netscape Search for" pulldown that appears as I type a URL is removed

IE 5.x has a similar feature, the difference being that you can change which search engine Mozilla uses; poke around a bit in the prefs.

there's no pop up alert when a site is unreachable (no one has "127.0.0.1 m.doubleclick.net" in their /etc/hosts anymore? hello?)

Run WinApache and get 404s (broken images or "Not Found" in an iframe) instead of "conn refused" popups.

Java is so slow.

Yet no one here ever complains about the slowness of PHP, Python, bash, etc. -- scripting languages that are almost by definition slower than Java in most circumstances. Why does the speed complaint only get leveled against Java?

The point is that, much like PHP, Java is plenty fast enough for what people use it for. I use it for web application development, and the performance is more that just acceptable. It's lightning fast. I think this perception is fostered by the ancient JVMs that ship with Windows and IE, which are major releases behind the current state of the art.

No one uses Java for GUI app development.

LimeWire, which IMHO is the best Gnutella client out there, is pure Java. It's very responsive, feature rich, stable, and less than 1MB, about the same size as XMMS. Hardly what you'd call slow bloatware, which is the usual complaint.

Sun owns Java. Java isn't free.

I could mention Tomcat, which is open source and which we use in production where I work. But then someone could complain that the JVM we're running it on is still proprietary to Sun...

Haven't any of you heard of Kaffe, GCJ, or GNU CLASSPATH? None of these things are what I would consider production-grade yet, but the point is, Java is only as closed as people want it to be. If you don't like the fact that the best JVMs are all proprietary, then by all means, contribute to one of the many free Java projects out there!

Get past the myths. Java won't solve every programming problem, but if you don't like it, at least complain about the parts that *do* suck (like java.io.* :)

Q

1. Make sure your ventilation ducts are too small to crawl through.

Ineffective if your enemy is allied with the borrowers[?].

7. Make sure your main computers have their own special operating system that will be completely incompatible with standard IBM and Macintosh powerbooks.

I might suggest OpenBSD. It's a nice server for servers and firewalls because if you don't know the password, it's incompatible with everything.

10. No matter how many shorts you have in the system, treat every surveillance camera malfunction as a full-scale emergency.

Bad idea because it would then open up a possible DoS: one of them will blow up the camera, which draws the guards away from the really valuable things.

12. Do not shoot at any of your co-workers if they are standing in front of the crucial support beam to a heavy, dangerous, unbalanced structure.

Better yet, hire some competent engineers <plug>who graduated from Rose-Hulman</plug> to design your structures, over-engineering them for safety.

18. Pad any data file of crucial importance to 1.45MB.

Won't help if your can get access to Apache or WinApache. Won't help if you can use dd to split files (a DOS dd fits on a floppy). Won't help if you can get access to a CD burner, as a 4x CD burner can burn 1.5 MB in five seconds (not counting ToC and closing the session).

The need for a graphical configuration tool has been acknowledged as important, even in the 2000 OSCon keynote, yet only about 15 people showed up for the Comanche presentation at the same conference. Getting such a tool packaged as part of the standard Apache dist is something that could happen if somebody championed it. There are plenty of choices for anybody motivated to pursue this. Problem is, a good champion would be someone who used a graphical interface him/herself, and most hackers (like me) prefer the text interface.

The Apache foundation is not only Apache httpd, it's got lots of tools which are prepared for the "web of services":

• All in the Apache XML project: Xerces, Xalan, Soap, Axis
• Many in the Jakarta Apache project, specially Cocoon and Tomcat

• So what if Apache is just a webserver? We can still use Tomcat!

The Apache foundation is not only Apache httpd, it's got lots of tools which are prepared for the "web of services":

• All in the Apache XML project: Xerces, Xalan, Soap, Axis
• Many in the Jakarta Apache project, specially Cocoon and Tomcat

• So what if Apache is just a webserver? We can still use Tomcat!

Check out JOnAS, which serves as the core for Enhydra. Both are functional, real-world application servers.

Check out Exolab, consisting of OpenEJB, OpenJMS, OpenORB, and more. Again, this is another open-source application server.

For web services, check out Apache SOAP. The wonderful folks at IBM have gifted the open source community with a SOAP/WSDL/UDDI implementation. There was some talk a while back about JBoss integrating Apache SOAP into its offerings, although the mailing list now causes me to doubt this.

Of course, I'm taking Mono and dotGNU.

What does all this add up to? It looks to me that Mono and dotGNU provide migration paths for existing MS customers. J2EE provides a software scalability that is not possible with Microsoft application servers. Between Sun, SGI, and IBM, the MS/Intel hegemony don't stand a chance with respect to hardware scalability. And with JBoss, Microsoft can't compete on price. It seems to me that the Unix camp will do quite well with this whole web services thing.

That said, it's not like one side will win while the other side loses. No matter what happens, MS will have a sizable camp of die-hard devotees. Likewise with the Unix camp. Somewhere in between, web services will support mixed solutions. Throw in non-MS implementations of the CRE, and the current quality of Java under Windows (it's still better than Linux...and, yes, I have tried the IBM VM), and we've got a situation where the underlying platform is really not that important. Finally, I'll get to focus on what I do best (programming), while avoiding all the religious hype surronding MS vs. Unix.

The percentage of IIS versus Apache is soon becoming irrelevant. What is important is the percentage of Servlet/JSP versus .NET/ASP sites. Which is kind of hard (impossible) to measure using Netcraft by the way.

One of the most succesful Servlet engines now is Tomcat, which is also open source coming from the Apache Jakarta project. I don't see any indication at the moment that the number of Servlet/JSP/J2EE sites is dropping in favour of ASP or .NET. No reason to worry yet.

I think the author has bought into the "Web Services!" hype and seriously over-estimates the problems in creating them.

Actually, Apache already has an XML "Web Service" framework in place - Cocoon. It seems to be pushed more as an HTML content server, but it can serve up XML just as easily.

The RPC equivalnet for web services, SOAP is available from the XML Apache project here. From my personal experience an excellent product , very easy to use and happily works with all kinds of "unsupported" servlet engines. However last time I saw it ( 7 months back ) , it couldn't speak to the Microsoft SOAP implementation because the SOAP header of Microsoft was sending the build number of the product as well as the standard header ;-) ... So much for platform independence of web services.

Naming/discovery equivalent for web services is available from the jUDDI project. It is hosted on sourceforge here

There may be others available as well but I am not aware of them.

As far as the article is concerned its too full of rhetoric ( Mozilla 1.0 on the client and Apache 2.0 on the server. How wonderful it's all going to be! Mozilla supports XUL and a cross-platform component object model! Oooh! It's more than a browser, it's an application platform! Aaah! And Apache 2.0 is both multi-process and multi-threaded, it has a new API for modules, and is so much more stable on Windows! Swoon! ) , based on weak statistics and just assumes all of us will believe "WebServices == Ultra Cool" without telling us why we should believe that.

The RPC equivalnet for web services, SOAP is available from the XML Apache project here. From my personal experience an excellent product , very easy to use and happily works with all kinds of "unsupported" servlet engines. However last time I saw it ( 7 months back ) , it couldn't speak to the Microsoft SOAP implementation because the SOAP header of Microsoft was sending the build number of the product as well as the standard header ;-) ... So much for platform independence of web services.

Naming/discovery equivalent for web services is available from the jUDDI project. It is hosted on sourceforge here

There may be others available as well but I am not aware of them.

As far as the article is concerned its too full of rhetoric ( Mozilla 1.0 on the client and Apache 2.0 on the server. How wonderful it's all going to be! Mozilla supports XUL and a cross-platform component object model! Oooh! It's more than a browser, it's an application platform! Aaah! And Apache 2.0 is both multi-process and multi-threaded, it has a new API for modules, and is so much more stable on Windows! Swoon! ) , based on weak statistics and just assumes all of us will believe "WebServices == Ultra Cool" without telling us why we should believe that.

There are a lot of cool projects going on over there, the most famous of which is Tomcat, an excellent (and free!) J2EE servlet engine (which Sun has made *the* reference implementation of their servlet spec). In the web services game, servlets are the point men. The author should have at least brought up the Jakarta name... although he probably would have lost his own arguement if he did :-P

Still, I think it was a good article overall. All the World War II analogies were quite entertaining.

There are a lot of cool projects going on over there, the most famous of which is Tomcat, an excellent (and free!) J2EE servlet engine (which Sun has made *the* reference implementation of their servlet spec). In the web services game, servlets are the point men. The author should have at least brought up the Jakarta name... although he probably would have lost his own arguement if he did :-P

Still, I think it was a good article overall. All the World War II analogies were quite entertaining.

Tired of applying patches to IIS? Tired of checking if your machine is infected with CodeRed? I've found the cure-all. And best of all, it's free!

He won't apologize. That would be admitting that Micro$haft created an inferior product. His ego would never let that happen. Hopefully more people will just dump IIS and run real web servers

New Code Red Worm patches here

Oh, and: Any halfway decent webserver allows you to run on another port -- they're only blocking port 80

Actually, I'm kind of irritated that you are making me defend Microsoft after all the bandwidth that has been chewed up over the last 5 days. I guess, by your rating, IIS is a "halfway decent webserver".

Microsoft IIS 4.0 to 5.0
1. Open Internet Service Manager.
2. Right-click the Web site that you want to change.
3. Click Properties.
4. Click the Web Site tab.
5. Change the TCP Port Number in the TCP Port edit box (or click Advanced for multiple Port settings).
6. Click OK to save the changes.


Moderators: I'm sorry for defending MS. I throw myself at your mercy.
use SD::Karma;$karma--;die("WTF");

Oh, and: Any halfway decent webserver allows you to run on another port they're only blocking port 80, not HTTP traffic in general (is that even possible?). You already have a shitty-looking address: h1290736218736078216472164230187467.mediaone.net what's wrong with adding an :81? ;)

I also think the cable company was probably quite pissed off over the Code Red hit their AUP specifically prohibits servers and here are hundreds of machines all running IIS webservers and making themselves quite visible.

Because there have been a few changes from version 1.3.14 which ships with OS X and the latest version 1.3.20 available from your friends at apache.org

Look, the people who are infected are too dumb to look after something as critical as a web server. The reason they got in trouble was because they were too dumb to keep up with patches. Don't go and do their work for them, or they will never learn.

What is the best way to learn? With a parent blasting you for a huge bandwidth bill. For your boss firing you for letting the company's database get owned. Having customers ripping you to shreds for destroying something important.

Not until they realise the severity of their actions will they begin to learn. Let them stew in their own "security patch" juices for a bit, and when they are done, pull them out and point them at alternatives.

As someone said before, otherwise you will hear conversations like this:

• Hey Bob, you fixed your server for that worm thinga-me-doo-what?
• Na Dave, I'm just waiting for the worm that patches it to come past. Someone will write one soon.

Basically, the market share for IIS is up slightly in the last month, but is still at only about 20%. Apache is way up near 60%.

My boss has just told our head of technical support to download the patches.
I said to our head of technical support "We don't need no steenkin' patches!"
Running Apache on Linux has turned out to be the right choice!

riiiight. Apache needs no patches

The tooth fairy will protect you.

I suspect this is the cure.

• Content comes from where it always comes from: people writing it in XML, or writing it in Word docs & having it converted to XML
• Where does it get stored? Any ol' file system will do.
• Where does the presentation come from? It's XML -- who cares? XSL, or the Xerxes Java parser on top of some HTML templates (as in Dynamo)... the Tomcat Struts engine handles XML nicely. It's XML. Just content. No presentation. That's the point.
• Where does that get stored? In your html docs directory. (these are all based on my experiences with teh ATG Dynamo engine... anyone who's worked with WebSphere or something else may have a diff't answer)

Try this for an example of how SVG could be used as a replacement.

http://nilo.stolte.free.fr/SVG.html#examples

Requires an SVG viewer.

Some are available for both Java and C++.

Sorry I don't have a more detailed answer to your question but I'm sure something can be built from the Apache XML stuff.

Mike

Well, if you search for Linux using this thing the first site you get is Debian, not linux.org. (Following that are Freshmeat and Apache, incidentally.)

Google's first hits, on the other hand, are linux.org, linux.com, and RedHat.

Could this be intentional?

Of course, you need Apache, Jakarta, Xerces, and so on. A bit tricky to mount, but all free.

JBoss Enhydra Jakarta Jetty jUDDI pUDDIng Resin

Just pick a project and start contributing ;-)

From the article:

What if I said the best thing that could happen to all of us is a complete backoff of all the bundling beyond what's specified in the W3C definition of the Web. Take Flash out. Take Java out...

Are we sure that we're just talking about the web here? The JRE gives the ability to run both applets in browser and normal Java apps... and it's not like there's a shortage of those