Cougaar 10.4.6 Released With Source 139
Anonymous Software Agent writes "Cougaar release 10.4.6 has been posted .
As always, all source code is available via anonymous CVS.
Cougaar is an open-source Java-based architecture for the construction of distributed agent-based applications. It is the product of an eight-year DARPA-funded research project in highly scalable and survivable multi-agent systems. Cougaar is currently used in next-generation military logistics systems, commercial applications, and research projects.
Cougaar release 10.4.6 adds survivable yellow pages and white pages services, and multiple other performance and reliability improvements."
I'm glad you explained what Cougar is (Score:2, Funny)
Re:I'm glad you explained what Cougar is (Score:5, Funny)
<ASH> Look! It's conducting rapid, large scale, distributed logistics planning and replanning!
<COUGAAR> COOOO-GAAAAAAAAAAAAAARRR!
Re:I'm glad you explained what Cougar is (Score:2)
More to the point (Score:4, Insightful)
Okay, I have a low opinion of Slashdotters that insist that software release announcements should stay on Freshmeat. I want to *know* when the next Linux kernel release and the next minor release of GNOME is, and it's big, discussable news.
However, this is a bugfix release of an obscure package. I realize that the editor was probably feeling more than a little whimsical, but dammit..can't Slashdot have an "Oddball" category? Stuff that the editor can dump things into if he sees something that whets his fancy, but is wildly unfit to go into the "News for Nerds" section? Things like "Lindows CEO Claims Microsoft CEO Porks His Sister" or "Random Extremely Obscure Package 10.4.6 Released" could go? It'd be a great grabbag for April 1.
Re:More to the point (Score:2)
They should create a "releases" section and put all this sort of stuff in there.
Then, for people like me, who don't care about the release of BSD 4.12343.137pre4 can hide the category and be done with it.
Re:More to the point (Score:2)
The big deal about this particular release was that the source code for this large DARPA-sponsored project is now accessible for browsing [cougaar.org] or for checking out with anonymous CVS [cougaar.org].
Re:I'm glad you explained what Cougar is (Score:1)
Then I read it, and got depressed... cuz now it means I have class in an hour.
DAMNIT! (Score:5, Funny)
Re:DAMNIT! (Score:2)
Unending confusion (Score:4, Funny)
Jeff Warren
www.ceggos.com [ceggos.com]
Even worse (Score:2)
Re:Unending confusion (Score:1)
Remember though that Mac OS X 10.4 as such will be called Cougar. Key features will be Exploite, Kliche, iSee and Safari version 2 (the one that finally supports ). Users will either be extatic, claim that all sorts of bus has not been fixed, or go
Re:Unending confusion (Score:1)
Re:Unending confusion (Score:3, Funny)
Re:Unending confusion (Score:3, Funny)
Coo gah wire
Not free (Score:4, Informative)
3. Licensee may use, sell or give away the Cougaar Software or any Derivative Work, alone or as a component of an aggregate software distribution containing Licensee Software, Cougaar Applications and/or programs from several different sources. No royalty or other fee is required. If Licensee sublicenses the Cougaar Software or Derivative Works, Licensee may charge fees for warranty or support, or for accepting indemnity or liability obligations of customers, provided that Licensee does not charge for the Cougaar Software or Derivative Work.
That along makes it unfree.
Re:Not free (Score:2)
I disagree, people can profit from it the same way they profit from other OSS projects. Without looking at it in depth, it seems to me a clone of the Mozilla Public License. Not Free in the GNU/Richard Stallman sense, but it does appear to meet the Open Source definition. If not, I'm sure ESR would be interested since they use the Open Source trademark.
Re:Not free (Score:1)
The more times I read that clause the less sense it makes. It begins very straight forwardly, saying "Licensee may use, sell or give away the Cougaar Software or any Derivative Work...". Okay, so, fine: I can sell it. The last part is where the double-take happens: "If [insert conditions here] provided that Licensee does not charge for the Cougaar Software or Derivative Work." I don't get it. Can I sell it, or can't I?
Perhaps the intended limitation is that if one intends to stand behind one's work for a f
Re:Not free (Score:5, Interesting)
It's quite explicit that you can "sell or give away the Cougaar Software or any Derivative Work". Case solved. You can sell it.
The second term is a bit puzzling. "If Licensee sublicenses the Cougaar Software or Derivative Works...Licensee does not charge for the Cougaar Software or Derivative Work". The key word here is "sublicenses".
You can sell the software or its derivatives all you want. Only if you sublicense it are you forbidded to charge for the software itself (though you may certainly charge for the media, bandwidth, support, manuals, etc). When you sublicense, the recipient is getting the license from YOU, not from the original author. This is a subtle distinction, and one few ever make in the Free Software World. What does it mean?
Not being a lawyer, I suspect it's primarily to mollify the legal types. Note that sublicensing is required to offer indemnity or liability (even if it weren't explicitly stated in the license). I suspect that this means if you create a business off of the software, you cannot sell the software itself, but only the warranty and support.
The license is Free as in FSF. Don't worry about it.
Re:Not free (Score:1)
The GPL lists [gnu.org] free software licenses, if you want to check their opinion on a license. Cougaar isn't listed.
The open source initiative [opensource.org] also lists licenses which qualify to be called Free Software. Cougaar isn't listed.
Is Cougaar using one of the listed licenses, or has it been sent to GNU for analysis?
Re:Not free (Score:3, Insightful)
Free Software isn't defined by lists of licenses. Open Source Software isn't defined by lists of licenses.
Re:Not free (Score:2)
Re:Not free (Score:2)
Cougaar folks, you need to get this fixed.
Re:Not free (Score:2)
A Good Read [fsf.org] about Free Software vs OSS.
Re:Not free (Score:2)
get their knickers in a knot about such
petty distinctions. It's free software, but
its not Free Software, likewise.
Re:Not free (Score:2)
John Sauter (J_Sauter@Empire.Net)
Sounds scary... (Score:4, Funny)
> scalable and survivable multi-agent systems.
> Cougaar is currently used in next-generation
> military logistics systems, commercial
> applications, and research projects.
Sounds like a certain Cyberdyne-developed distributed neural-net supercomputer that could integrate all of the USs strategic arsenal under a single command structure, and would survive a nuclear armagedden... gulp... lets just make sure there is a deadman backdoor switch.
Re:Sounds scary... (Score:3, Funny)
screw that, i just want to make sure we get hot naked cyborg chicks from the future out of the deal
Re:Sounds scary... (Score:1)
Re:Sounds scary... (Score:1)
Well arnie's in government now, and you thought terminator was a work of fiction - the t800 realised the only way to deal with the problem was via the democratic process. Skynet funding bill - denied!
I think this is the future of computing. (Score:4, Insightful)
Like the Internet, but with other goals than networked communications. I think this is the sort of thing that will finally bring the convergence that was always talked about in regards to the Internet (an alarm clock, coffee, toaster, car starter, etc. that are aware of your schedule, not unlike the opening scene of Back To The Future).
Does C# have anything like this, or is this easily portable to C# or any other strongly typed portable languages such as Python? It'd be nice to have another alternative to Java, which seems to cause problems for some people.
Re:I think this is the future of computing. (Score:3, Informative)
This is false by any definition of strong typing I've seen. This isn't even something one can have an opinion on, it's just wrong.
Portrait of a strongly typed language:
>>> a="some string"
>>> a + 5
Traceback (most recent call last):
File "", line 1, in ?
TypeError: cannot concatenate 'str' and 'int' objects
In a weakly typed language (i.e. perl), the statement will just break in mysterious ways:
$a="some string";
$a = $a + 5;
print "$a\n";
(prints
Re:I think this is the future of computing. (Score:2)
$a="some string";
$a = $a + 5;
print "$a\n";
(prints 5)
If you use '-w' with Perl, as is recommended by virtually every Perl guru in existence, you get:
bash$
Argument "some string" isn't numeric in addition (+) at
5
That seems pretty non-mysterious, doesn't it?
-chris
Re:I think this is the future of computing. (Score:2)
bash$
Argument "some string" isn't numeric in addition (+) at
5
That seems pretty non-mysterious, doesn't it?
You still got 5. Your program still broke. However, if you look around through wherever that log goes when it made it to ``production,'' you might have a clue as to what the condition was that caused it to break.
Develop Much? (Score:2)
Re:Develop Much? (Score:2)
Because if a user gets a message like "Traceback (most recent call last): File "", line 1, in ? TypeError: cannot concatenate 'str' and 'int' objects" then you might as well have said "5", it'd be about as meaningful.
There is a *huge* difference between getting the wrong answer (5) and getting an exception. As frustrating as an error may be for a user, it's far, far better than misleading the user.
Lets face it: the only languages suitable for a production environm
Re:Develop Much? (Score:2)
angel'o'sphere
Re:Develop Much? (Score:2)
Have a cache in a top level classloader, cache something in a lower classloader, and then pull it out from a peer classloader.
This has bitten me a few times when I've got a utility set of classes that include a class and are in the classpath of a servlet container. Each webapp trying to use the cache sees the others namespace, but can't make any sense of the objects in the cache.
Re:I think this is the future of computing. (Score:1)
Re:I think this is the future of computing. (Score:3, Insightful)
I'm Not Let'n No Dynamic Code Run on *My* Computer (Score:2)
Re:I think this is the future of computing. (Score:2)
I did some research on agent technology when I was in grad school, related to controling mobile robots. I understand why you'd need agents in that context.
I can also see some uses on distributed web searches, information foraging, stuff like that.
But now I'm working for a certain large consulting company that has now decided to branch into making Xbox chips...I've been writing apps for insurance companies, governments, etc. I'm not sure how agent
Re:I think this is the future of computing. (Score:2)
Nothing wrong with Java...it is becoming quite ubiquitous everywhere except Windows client-side programming, and it may make a comeback there. There is no production-quality C# solution for Linux, most Unixen or the Mac yet, whereas Java is quite mature and fast. gcj (though not a Jav
Erlang was DESIGNED for this (Score:2)
Java is a far worse contender for such a project. Unless you hate functional style.
Re:I think this is the future of computing. (Score:2)
Ah yes, that's why DARPA funded this, to
KILL PEOPLE in a POSITIVE way.
As opposed to NEGATIVE uses like SHARING
ENTERTAINMENT.
Big Cats? (Score:1, Redundant)
Don't fall for it! (Score:3, Funny)
> Cougaar is an open-source Java-based architecture for the construction of distributed agent-based applications.
I heard it was just a variant of the Nigerian e-mail scam.
8 years and Java based? (Score:1)
Re:8 years and Java based? (Score:5, Insightful)
HotJava was released in early 1995, iirc. that was why we upgraded to solaris from sunOS. You know, so we could play tic-tac-toe like it was 1978!
Re:8 years and Java based? (Score:2)
(if you don't get the joke, you're under 25
Not quite done yet... (Score:4, Insightful)
...needs more buzzwords.
Re:Not quite done yet... (Score:1)
"Cougaar release 10.4.6 has been posted . As always, all source code is available via anonymous CVS. Cougaar is an open-source Java-based cyber-architecture for the construction of distributed cyber-agent-based applications. It is the product of an eight-year DARPA-funded cyber-research project in highly scalable and survivable multi-agent cyber-systems. Cougaar is currently used in next-generation military logistics cyber-systems, commercial applications, and research cyber-projects. Cougaar r
Re:Not quite done yet... (Score:2)
Good release testing strategy (Score:5, Funny)
2. Install shiny new distributed agents on Web servers
3. Announce new release on Slashdot
4. Examine performance of Web server agents under extreme load. Saves all that expensive load testing time and expense...
5. Announce new "stress tested version" shortly afterwards
You forgot (Score:2)
Re:Good release testing strategy (Score:3, Interesting)
> under extreme load. Piece of cake.
The Cougaar FAQ (Score:4, Informative)
Posted anonymously to prevent carma whoring, since 2001.
Re:but what is it?! (Score:4, Informative)
You can understand why this is attractive, it would make the "system that keeps running even though part of it is nuked" closer to reality. It would also take P2P and distributed computing to a new level.
While it is interesting in theory, they usually run into problems when implementing it in practice. If you think about it, the "moving over the net and executing wherever" sounds a lot like a virus, right? Therefore, they have to make a sandbox on the server for the agents to play in, so that they don't access sensitive data, or crash the host computer by using up all resources etc. Also, the agent and its contents have to be protected from potentially malicious hosts, so that they don't get sensitive data exposed or corrupted.
So when you apply all the security checks and encryption you need, the sandbox and agents become very bloated and slow to execute. Bloated agents move very slowly over the network and take up bandwidth... not good.
Aglets is an early Java based test system for this, the name stands for "agile applets".
593 downloads as of now ... (Score:1)
CC.
1214 downloads as of now ... (Score:1)
CC.
Ah... (Score:1)
With all the hype about SuSE and Novell... (Score:1, Redundant)
...I thought I had slept through another OS X release for a second!
Java was a mistake for this project (Score:5, Interesting)
In those languages distributed programming itself is solved more elegant and error proof. Besides, they have very strong mechanism of constraint logic. Even more - distributed constraint logic. And no need to repeat that functional programming languages are more effective for complicated logical tasks.
Oppositely, in Java the agent developer feels like in assembly. Don't repeat me the mantra about the garbage collector: functional programming languages have it since 1957 (first Lisp).
Well, if brains of their project decision makers are already corrupted by procedural programming (or even worse - by merketing hype of Java) then nothing can fix that. It's just one more government-wasted effort.
Re:Java was a mistake for this project (Score:5, Insightful)
While people have certainly been programming mobile agents in many languages for a very long time, there's nothing wrong with implementing them in Java. Java is a fairly nice language with a good security model and portable bytecode. Having used both to write agents, I can say that it's not quite as nice for writing mobile agents as Telescript (the language that General Magic designed for implementing mobile agents), but it's not bad. Sure, SmallTalk or Lisp are simpler and cleaner in many ways, and Erlang, etc., have some nice, though somewhat esoteric advantages, but Java has the fairly reasonable advantages that it's a widely known and extremely well supported language.
And as for preferring declarative programming to procedural programming, well, all I can say is that different models suit different kinds of problems, and different kinds of programmers. Changing both programming languages and programming paradigms (i.e. procedural to declarative) and throwing mobile agents into the mix) is extemely challenging to a development team. Not that it can't be done, but it's way harder (for a large team) than just introducing mobile agents implemented in a language everyone knows. Take one step at a time, or you lose people. I know, back in the 80's I was on a number of large Smalltalk projects, and making the leap to OOP, Client/Server and learning Smalltalk all at once was a barrier than many engineers couldn't hurdle. Sure, the stars got it, and were amazingly productive, but everyone else was blocked.
That being said, if you have a small team of stars, and a project that doesn't require a larger team, go for it -- you may be extremely successful. But I don't think that makes anyone who decides to implement mobile agents in Java wrong, just a little less daring.
Re:Java was a mistake for this project (Score:1)
Sure, in Java it is probably harder to write these kinds of distributed agents, but a lot more people can hack all kinds of interesting stuff onto the agents just because they can read Java code.
just mod me down to flamebait
--Blerik
Re:Java was a mistake for this project (Score:1)
I used to work in telecommunications and I've used C, C++, Erlang and Java to write server / client code in and they're all pretty good fits (well, C and C++ are nicer for networking in Unix than Windows IMO but YMMV).
Java's main selling point for this kind of work is that it manages complexity extremely well, and has very efficient networking and threading.
You claim that the project's decisi
Re:Java was a mistake for this project (Score:1, Flamebait)
Re:Java was a mistake for this project (Score:2)
Are we talking about the same language that requires a SEPERATE THREAD for every network connection?? Thats not what I'd call efficient,
convenient or logical.
Re:Java was a mistake for this project (Score:1)
Re:Java was a mistake for this project (Score:2)
I do know that Cougaar developers use Linux, Windows and OSX, so portability is a reality here.
Functional programming? Enough already! (Score:2)
1) Functional languages are NOT more efficient. They are complex, convoluted and utterly non intuitive.
2) Procedural programming follows the way people think. Functional doesn't.
3) Garbage collection? Is that supposed to be a GOOD thing?? If you want efficient binaries you do your own memory management.
4) Functional programs are NOT less bug prone.
That was quick (Score:1)
Wrong name? (Score:1)
Maybe it should be renamed "Smiith". :-)
so really.... what is this thing useful for. (Score:1)
It sounds to me like this project, like many others before it, is headed down a spiral of software uselessness really fast. They've already lost my vote. It seems pretty useless to me.
Re:so really.... what is this thing useful for. (Score:3, Interesting)
The idea behind an agent is that you create a semi-autonomous piece of software that can communicate with other agents, get information from other agents and the surrounding environment, and take actions based on
Red Dwarf (Score:2, Funny)
Cougaar? (Score:2)
Business Straategy (Score:3, Funny)
2. Aad aa few extraa 'aa's.
3. Profit!
Almost thought it was an OS X update... (Score:1)
Apple has ruined using feline monikers for software.
Re:Almost thought it was an OS X update... (Score:2)
Re:Habete Mirrorum (Score:1)
Re:What really is cougar (Score:1)