I am pleased to announce that Javafu.com is now up & running.

A lot of this came out of ideas drawn from this discussion.

I am not using the Everything Engine. This site was written completely in server side java. Though for the time being you might find the layout very very similar to the Dark Theme offered here.

Just as perlmonks is a metaphor for a place where one may study peacefully & reflect, Javafu is a metaphor comparing martial arts to software development.

Also, as some of you know, I am championing the CJAN Project, which could hopefully become as valuable a resource to the Java community as the CPAN is to the Perl community. The official project is on Sourceforge.

I have learned & grown a lot from visiting here, as I'm sure a lot of us have. This is my way of giving back. I hope you find it of some use.

So, without further ado, I give you:

Javafu.com


Wait! This isn't a Parachute, this is a Backpack!

Replies are listed 'Best First'.
Re: ANNOUNCE: JavaFu.com Open For Business
by perrin (Chancellor) on Jan 16, 2002 at 04:33 UTC
[reply]
Re: ANNOUNCE: JavaFu.com Open For Business
by talexb (Chancellor) on Jan 16, 2002 at 07:36 UTC
    Javafu.com may be open for business, but it appears to be behind something like a firewall: 
    bash-2.04$ ping -c 10 javafu.com
PING javafu.com (216.168.224.70): 56 data bytes
36 bytes from sl-gw2-rly-0-0-0.sprintlink.net (144.232.25.251): Commun
+ication prohibited by filter
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 7a36   0 0000  fa  01 ba73 209.68.1.203  216.168.224.70

    [download]
    Time now 2137 EST Tuesday January 15.

    --t. alex

    "Of course, you realize that this means war." -- Bugs Bunny.

[reply]
[d/l]
      In fact, it is not behind a firewall. What is IS behind is my ISP, who filters port 80, claiming that they're doing so due to the 'Red Alert' virus. This is a blatant lie, where they charge businesses 3 times what they charge me for the same service, just to allow access to port 80. Because you know, a single home user would never run a web server right? Ugh... I called & told them "I don't even use windows!" but they are conveniently ignorant as to what the hell I'm talking about. "What's a port?" I got back... nice eh?

      So naturally, I rerouted everyone to port 81 via the DNS server, which is off-site. This solves the problem, unless YOUR firewall doesn't let you out through 81... Which now seems to be a recurring problem with a number of users...

      Time to switch ISP's I think...

      OR, I might try pushing traffic over to port 443. I'll have to see if they've filtered that one too... :\

      Also, just for nothing, I usually kill ping & finger anyway, so relying on just that isn't enough. No mac servers (<OSX) implement ping, for example.



      Wait! This isn't a Parachute, this is a Backpack!
[reply]

Back to Meditations