From f844f89eae41ff16153dc2b25c0706c6dffbd205 Mon Sep 17 00:00:00 2001
From: Trevor Johnson <trevor@FreeBSD.org>
Date: Sat, 10 Apr 2004 17:11:02 +0000
Subject: Cram into 80 columns by 24 rows.
---
devel/flick/pkg-descr | 46 +++++++++++++++++++---------------------------
1 file changed, 19 insertions(+), 27 deletions(-)
(limited to 'devel/flick')
diff --git a/devel/flick/pkg-descr b/devel/flick/pkg-descr
index be0ce1730cff..1c44f1601ff8 100644
--- a/devel/flick/pkg-descr
+++ b/devel/flick/pkg-descr
@@ -1,31 +1,23 @@
-Flick is an interface definition language (IDL) compiler ("stub generator")
-supporting remote procedure call (RPC) and remote method invocation (RMI) for
-client/server or distributed object systems. What sets it apart from other IDL
-compilers is that it is highly optimizing while also supporting several IDLs,
-message formats, and transport mechanisms. Flick currently has front ends for
-the CORBA, Sun ONC RPC, and Mach MIG IDLs, and middle and back ends that support
-CORBA IIOP, ONC/TCP, MIG-style Mach messages, and Fluke IPC (see below). Flick
-produces stubs in the C language. A substantial user's manual is provided.
+from the Web page:
-Flick is designed to be a "kit": the user picks the IDL, language mapping, and
-transport components that are required for any particular system. Our goal is
-to make it straightforward to add new components to the kit to process new
-IDLs, language mappings, and transports. (Collaborators welcome!) Flick's
-framework can also be used to support interface annotation. Full source for
-the Flick compiler is distributed under the terms of the GNU General Public
-License; source for the Flick runtime is distributed under a BSD-style license.
+ Flick, our IDL (interface definition language) compiler, is the research
+ and production IDL compiler within the Flux Project. Flick uses
+ techniques from traditional language compilers in order to produce very
+ fast client/server communication code. Flick-generated code can
+ typically encode and decode data between 2 and 17 times faster than code
+ produced by traditional IDL compilers, both commercial and free. The
+ result is that on stock hardware and operating systems, Flick-generated
+ stubs can increase end-to-end application throughput by factors of 4 or
+ more.
-Flick-generated marshal and unmarshal code generally runs between 2 and 17
-times as fast as code produced by other IDL compilers, commercial and free. On
-stock hardware and operating systems, Flick-generated stubs can increase
-end-to-end client/server throughput by factors between 1.2 and 3.7 or more.
-
-Our paper describing these results was presented at PLDI'97, the major compiler
-conference, in June (see http://www.cs.bu.edu/pub/pldi97/). The paper is
-included as part of the Flick distribution, and is separately available at
-ftp://mancos.cs.utah.edu/papers/flick-pldi-97-abs.html.
-
-Jay Lepreau, lepreau@cs.utah.edu
-University of Utah Computer Science Dept.
+ Flick is not just optimizing: it is also extremely flexible. Flick
+ currently supports the CORBA, ONC RPC (Sun RPC), and MIG IDLs.
+ Interfaces written in any of these languages can be implemented by
+ CORBA-, ONC RPC-, or MIG-style C language ``stubs'' communicating via
+ CORBA IIOP, ONC/TCP, Mach 3 ports, Trapeze, or Fluke IPC. Flick also
+ generates optimized CORBA C++ stubs that work with TAO, the real-time
+ CORBA ORB. Finally, because Flick is a ``kit'' of components, it can be
+ extended to support new IDLs, message data formats, and transport
+ mechanisms.
WWW: http://www.cs.utah.edu/flux/flick/
--
cgit v1.2.3