Weekly Edition
Return to the Press page
| |||||||||||||
Interview: JOLIE and Service-Oriented Computing Explained (KDE.News)
KDE.news has an interview with Fabrizio Montesi, one of the developers of the JOLIE language for "service-oriented computing". "Which is what JOLIE is all about - a generic programming language for programming any kind of service or service-oriented architecture, independent of the underlying protocols (JOLIE abstracts the communication away, e.g. D-Bus apps can communicate with a SOAP-based service through JOLIE). And of course, this is incredibly easy to use. In most other languages you'd find it is very hard to write service-oriented code, but JOLIE is all about services."
(Log in to post comments)
Interview: JOLIE and Service-Oriented Computing Explained (KDE.News) Posted Sep 9, 2008 5:26 UTC (Tue) by roskegg (subscriber, #105) [Link]
This sounds like CORBA done right. Twenty years later...
Interview: JOLIE and Service-Oriented Computing Explained (KDE.News) Posted Sep 9, 2008 7:11 UTC (Tue) by Cato (subscriber, #7643) [Link]
Can anyone explain why yet another new language is necessary, rather than simply a library? The site is down so it's hard to see what this is about, though.
Interview: JOLIE and Service-Oriented Computing Explained (KDE.News) Posted Sep 9, 2008 15:55 UTC (Tue) by aseigo (guest, #18394) [Link]
There's no short explanation to this, but the gist of it is that the difference between a language and a
library in this case is that the language is more straightforward to use. It's designed to express quite clearly the sort of things you need to in setting up ad hoc SOA systems; you could certainly do it with a library API only but it'd be even more cumbersome to use. The language itself is pretty basic and focused (not meant to replace any other language, for instance). Think of it as the replacement for XML based descriptions used by some other SOA frameworks. It's just a design choice, and one that seems sensible so far. Maybe one day someone will wrap it all in a higher level API, who knows. ;)
|
|||||||||||||