communicator-user — Galaxy Communicator User Discussion List

Re: [Communicator-user] Non-open-source discussions

[Samuel L. B. <sa...@li...>]

   Date: Thu, 19 Apr 2001 16:04:48 -0400
   From: Dave Stallard <sta...@bb...>
   X-Accept-Language: en
   CC: com...@li...
   Content-Type: text/plain; charset=us-ascii

   "Samuel L. Bayer" wrote:
   > 
   > All -
   > 
   > Jim Bass's interest in starting a discussion about W3CVB has made it
   > clear to me that some of the conversations we want to have as DARPA
   > Communicator participants are arguably inappropriate for this mailing
   > list, which is intended for discussion about the Galaxy Communicator
   > infrastructure. I'm leaning toward setting up a separate mailing list,
   > on a MITRE server, for program discussions. Does anyone have any
   > strong feelings about this issue one way or another?

   Isn't that what the advisory committee is for?

    Dave

Interesting. That list's been dead for a while. I'll bring this up
with Jim.

Sam

[Communicator-user] Galaxy Communicator and W3CVB

[Samuel L. B. <sa...@li...>]

All -

Here are my initial thoughts on the relationship between W3CVB and the
Galaxy Communicator infrastructure.

Over the years, I've personally reviewed many of the W3CVB documents,
and none of them have alarmed me from the point of view of the Galaxy
Communicator effort. It's important to remember that W3CVB and GC are
trying to do very different things on a number of dimensions:

- First, the W3CVB proposals are all proposals for data
  description. None of them address the issues of infrastructure
  connectivity or the issues of service definitions. So it's perfectly
  conceivable that a Communicator-compliant server might also be
  completely compliant with the relevant W3CVB standards proposals.

- Second, the W3CVB proposals are attempting to standardize current
  technology for the purpose of current market exploitation, while GC
  is attempting to support a development infrastructure for the
  purpose of dialogue research and future market insertion and
  exploitation. So we can expect that there are capabilities which
  W3CVB won't envision (such as mixed initiative dialogue) which are
  very important from the point of view of GC.

With that in mind, I'll try to address Jim's three questions. Some of
these questions are program-level questions, rather than
technology-level questions; with apologies to the non-Communicator
participants listening in, I'll address those dimensions as well.

1. Is the proposed solution helpful or hurtful for Galaxy Communicator
work?

I believe that some of the W3CVB standards are very relevant to
Communicator, such as the speech synthesis markup standards. Others,
like VoiceXML, aren't compatible with GC goals like mixed initiative
dialogue, but shouldn't be expected to be, since W3CVB is a near-term
effort. Additionally, since the work in mixed-initiative dialogue
isn't ready to be standardized yet, the appropriate thing to do in my
mind is to use these near-term proposals as a baseline so that we can
be more responsive to the established community when it comes time to
propose a more flexible standard.

2. Should DARPA through MITRE (and MIT, IBM, et. al.) have an input?

Everyone on this mailing list ought to be reading the W3CVB
documents. The W3CVB effort is a broad effort with a good deal of
industry support. For MITRE's part, we've provided considerable
feedback to the W3CVB committee on their proposals already; I'm hoping
that others in the program have as well.

3. What issues are key for the Communicator program to follow?

For a dialogue research program, the importance of standards is
unclear. Plug and play at the message level is useful, but any
well-documented message set ought to be readily digestible by a
Communicator developer. Nevertheless, I think we ought to start a
conversation about these things for more well-understood services,
since these efforts are complementary to W3CVB. Plug and play at the
data level can also be useful, but given the cutting-edge nature of
the Communicator work program, I think it's more important for us to
digest the appropriate proposed standards rather than proposing
standards ourselves.

If there's interest, I'll attempt to summarize the points of
similarity and contrast between the current W3CVB documents and the
Galaxy Communicator effort in a subsequent message.

Sam

Re: [Communicator-user] Non-open-source discussions

[Dave S. <sta...@bb...>]

"Samuel L. Bayer" wrote:
> 
> All -
> 
> Jim Bass's interest in starting a discussion about W3CVB has made it
> clear to me that some of the conversations we want to have as DARPA
> Communicator participants are arguably inappropriate for this mailing
> list, which is intended for discussion about the Galaxy Communicator
> infrastructure. I'm leaning toward setting up a separate mailing list,
> on a MITRE server, for program discussions. Does anyone have any
> strong feelings about this issue one way or another?

Isn't that what the advisory committee is for?

 Dave

[Communicator-user] Non-open-source discussions

[Samuel L. B. <sa...@li...>]

All -

Jim Bass's interest in starting a discussion about W3CVB has made it
clear to me that some of the conversations we want to have as DARPA
Communicator participants are arguably inappropriate for this mailing
list, which is intended for discussion about the Galaxy Communicator
infrastructure. I'm leaning toward setting up a separate mailing list,
on a MITRE server, for program discussions. Does anyone have any
strong feelings about this issue one way or another?

Thanks,
Sam

[Communicator-user] [jbass@darpa.mil: New call control language requirements for the W3C Speech Interface Framework]

[Samuel L. B. <sa...@li...>]

All -

Jim Bass, the program manager for the DARPA Communicator program, has
asked me to facilitate a conversation about the following document:

	http://www.w3.org/TR/call-control-reqs

As many of you know, this is one of the documents that the W3C Voice
Browsers activity has generated in the context of making a set of
proposals for telephone-based dialogue capabilities. A number of the
folks involved in the DARPA Communicator program are also involved in
W3CVB. The documents that have been generated under this activity can
be found at http://www.w3.org/Voice. These documents include proposals
(in varying states of completion) for speech grammars, dialogue
descriptions (using VoiceXML, essentially), synthesis markup,
multimodal interaction, and NL semantics.

His complete message is attached. I will contribute my own view in a
later message.

Sam

------- Start of forwarded message -------
From: jbass <jb...@da...>
Subject: New call control language requirements for the W3C Speech Interfa
	ce Framework
Date: Thu, 19 Apr 2001 14:17:49 -0400

Everyone,

We need information, and I would like Sam to be the primary for this.

	http://www.w3.org/TR/call-control-reqs

Issues:

1.  Is the proposed solution helpful or hurtful for Galaxy Communicator
work.
2.  Should DARPA through MITRE (and MIT, IBM, et. al.) have an input?
3.  What issues are key for the Communicator program to follow?

By the way, I want something about this presented in New Orleans.

This is a critical time event.  We have a lot to contribute to the work - we
have a major portion of the community.  We CANNOT assume ready acceptance of
our work at the W3C.  We must step up, present, defend, and advocate our
technology.  Do WE believe in Communicator and the Galaxy architecture?  I
do!  So let's get it beyond our community out to the W3C.

Sam, pass this through the listbot so everyone knows our thinking and
concerns.

Thanks,

Jim

James D. Bass, Ph.D.
Lieutenant Colonel, United States Army
Program Manager - Information Technology Office
* * * * *
DARPA-ITO
3701 North Fairfax Drive
Arlington, VA 22203-1714
* * * * *
Office:  703.696.2227
Fax:  703.696.4534
SETA: Tracie Smith 703.522.6067, ext. 153 
------- End of forwarded message -------

[Communicator-user] Unscheduled fofoca downtime

[Samuel L. B. <sa...@li...>]

All -

Due to circumstances beyond our control, fofoca.mitre.org will be
unavailable for a few days. We apologize for the inconvenience. 

Samuel Bayer
The MITRE Corporation
sa...@mi...

RE: [Communicator-user] Communicator internationalization?

[jbass <jb...@da...>]

Everyone,

The Amities project (initiated by the EU with US players - DARPA funded) is
the first major step at internationalizing dialog technology within the
DARPA research community.  Amities is based on the call-center paradigm.  I
will require the US Amities participants to present their work at future
Communicator meetings.  I am working with Allen Sears and Victor Zue on an
extension of Communicator (code name - Symphony) to carry dialog research
beyond 2002.  Share your ideas with Allen, Victor, or me.  This is a
critical time in the future of dialog research.  Can Galaxy cross
international lines?  How should MT fit in our dialog research agenda, if at
all?  Get your thoughts in the discussion.

What is Amities?  Check out their URL:
http://fm.hltcentral.org/projects/FMPro?-db=projectsdb.fp5&-format=summary.h
tml&-lay=detail&-sortfield=Acronym&FirstLetter=A&Status=accepted&-max=20&-re
cid=32836&-find=&-token.9=ListAlpha.html&-token.8=5

Sorry for the lllloooonnnngggg URL, you know those crazy Europeans! ;-)

Jim

James D. Bass, Ph.D.
Lieutenant Colonel, United States Army
Program Manager - Information Technology Office
* * * * *
DARPA-ITO
3701 North Fairfax Drive
Arlington, VA 22203-1714
* * * * *
Office:  703.696.2227
Fax:  703.696.4534
SETA: Tracie Smith 703.522.6067, ext. 153 


-----Original Message-----
From: Samuel L. Bayer [mailto:sa...@li...]
Sent: Tuesday, April 03, 2001 3:36 PM
To: com...@li...
Subject: [Communicator-user] Communicator internationalization?



All -

Over the last few weeks, a number of people have asked me about how
hard it would be to internationalize Communicator. I freely admit that
I have barely the faintest idea what that might mean, besides
(perhaps) introducing a wide string datatype. Has anyone thought about
this issue?

Thanks in advance -
Sam Bayer
The MITRE Corporation
sa...@mi...



_______________________________________________
Communicator-user mailing list
Com...@li...
http://lists.sourceforge.net/lists/listinfo/communicator-user

Re: [Communicator-user] Communicator internationalization?

[Scott C. <cy...@sl...>]

> Over the last few weeks, a number of people have asked me about how
> hard it would be to internationalize Communicator. I freely admit that
> I have barely the faintest idea what that might mean, besides
> (perhaps) introducing a wide string datatype. Has anyone thought about
> this issue?

Internationalization could mean making all the tihngs Communicator prints
out obey the localization settings.  This is a lot of work.

If it is "just" a matter of building multi-lingual systems, then
Communicator is out of the picture if the servers can agree on a standard
character encoding such as UTF-8, Big5, etc.  (CJKV Information Processing
by Ken Lunde is a good resource for the harder cases: Chinese, Japanese,
Korean, and Vietnamese).  None of this is very pleasant in C/C++.

[Communicator-user] Communicator internationalization?

[Samuel L. B. <sa...@li...>]

All -

Over the last few weeks, a number of people have asked me about how
hard it would be to internationalize Communicator. I freely admit that
I have barely the faintest idea what that might mean, besides
(perhaps) introducing a wide string datatype. Has anyone thought about
this issue?

Thanks in advance -
Sam Bayer
The MITRE Corporation
sa...@mi...

[Communicator-user] .

[<jk9...@ya...>]

The Internet's Finest and Most Reliable Bulk Email Provider!

Since 1996, Tech Data Technologies has provided bulk email service to thousands of well-satisfied customers. We offer the most competitive prices in the industry, made possible by our high percentage of repeat business. We have the most advanced, direct email technology, employed by only a knowledgeable few in the world. 

We have over 160 million active email addresses, increasing our list at the rate of half a million to one million a month. We will put your product or service instantly and directly into the hands of millions of prospects! You will have instant, guaranteed results, something no other form of marketing can claim. Our turn around time is a remarkable 24 hours.

Our email addresses are sorted by country, state, city and target. Your marketing campaign will speed with pinpoint accuracy to your desired audience!

Call us for a free consultation at 323 876 6148  [U.S.A.]. 

For a limited time, take advantage of our special -- Three million general U.S. emails for just $600 per million! We include, at no cost, a bullet proof email address for 30 days, a $400 value!

BULK EMAIL PRICES

  750,000........................$562
1,200,000........................$720
1,600,000........................$960
3,000,000........................$1,500
3,000,000+ ...................PLEASE CALL FOR A QUOTE


Best of ALL, Tech Data Services can be used as a 100% TAX WRITE OFF for your Business!


DON'T WAIT! LET TECH DATA TECHNOLOGIES BE YOUR PARTNER!!


Under Bill s.1618 TITLE III passed by the 105th U.S. Congress this letter is not considered "spam" as long as we include: 1) contact information and, 2) the way to be removed from future mailings (see below).To Remove Yourself From This List: Please email see...@ya... with the email address that you would like removed and the word REMOVE in the subject heading.

[Communicator-user] Announcing the release of GalaxyCommunicator version 3.0beta4

[Samuel L. B. <sa...@li...>]

All - 

We are, as usual, pleased and relieved to announce the availability of
Galaxy Communicator 3.0beta4. This is the final beta for version 3.0;
the only changes from the previous public beta (3.0beta2) are minor
bug fixes. Even though the internals of the infrastructure have
changed in some major ways, the upgrade from 2.1 to 3.0 will be quite
simple for the great majority of users. Version 3.0 features:

o Vastly improved tools for managing simultaneous sessions 

o More flexible and robust Hub-server interaction, including the
introduction of continuations and the elimination of deadlocks  

o Support for server location files, which help maintain consistent
port location information across Hub and server  

o Many infrastructure improvements, including cross-language support
for distinguishing among Galaxy Communicator versions, improved timed
task control, and a consistent, event-driven programming model for
embedding the Galaxy Communicator library  

o Improvements in the frame library, including support for dynamically
expandable lists and arrays, better memory management options, and
access to the full range of Communicator types as frame fills 

o More flexibility in the Hub syntax and organization, including
better management of servers and service types, new support for
choosing among available servers, and an alternative syntax which
provides a wider array of control options and eliminates some of the
idiosyncracies in the default syntax  

o A completely revised communications protocol, including XDR encoding
for all brokering and message traffic and better encapsulation of
administrative information  

o Significant brokering improvements, including access to the full
range of Communicator types for brokering and automatic support for
multiple subscribers for outgoing brokers 

o A PDF version of the HTML documentation (thanks to
http://www.easysw.com and their open source conversion tool!)

The test period for 3.0 has been relatively long, and we anticipate no
obstacles to releasing version 3.0 final on the week of April 16,
2001. Please direct all bugs, as usual, to
bug...@li...; please do not send mail directly to
members of the Communicator team.

The GalaxyCommunicator 3.0beta4 distribution comes with extensive
documentation (see docs/index.html), a detailed list of new features
(see docs/new_features.html), and an upgrade guide for 2.1
installations to 3.0beta4 (see docs/3point0upgrade.html). Upgrade
assistance and guidance is also available at
bug...@li....

The GalaxyCommunicator 3.0beta4 release is an open source
distribution. It is available at http://fofoca.mitre.org/download.

Samuel Bayer 
For the Communicator team 

P.S. MIT Galaxy users: The MIT Galaxy system will not compile against
Galaxy Communicator 3.0 without minor modifications. MITRE has a set
of working patches, which you may contact me directly in order to
obtain.

[Communicator-user] Announcing GalaxyCommunicator 3.0beta2

[Samuel L. B. <sa...@li...>]

All - 

We are, as usual, pleased and relieved to announce the availability of
Galaxy Communicator 3.0beta2. Version 3.0 has been under development
since late summer, and this beta is complete; the code has been frozen
since late December. Even though the internals of the infrastructure
have changed in some major ways, the upgrade from 2.1 to 3.0 will be
quite simple for the great majority of users.  Version 3.0 features:

    1. Vastly improved tools for managing simultaneous sessions 
    2. More flexible and robust Hub-server interaction, including the
       introduction of continuations and the elimination of deadlocks  
    3. Support for server location files, which help maintain
       consistent port location information across Hub and server  
    4. Many infrastructure improvements, including cross-language
       support for distinguishing among Galaxy Communicator versions, 
       improved timed task control, and a consistent, event-driven
       programming model for embedding the Galaxy Communicator library  
    5. Improvements in the frame library, including support for
       dynamically expandable lists and arrays, better memory management 
       options, and access to the full range of Communicator types as
       frame fills  
    6. More flexibility in the Hub syntax and organization, including
       better management of servers and service types, new support for 
       choosing among available servers, and an alternative syntax
       which provides a wider array of control options and eliminates 
       some of the idiosyncracies in the default syntax 
    7. A completely revised communications protocol, including XDR
       encoding for all brokering and message traffic and better 
       encapsulation of administrative information 
    8. Significant brokering improvements, including access to the
       full range of Communicator types for brokering and automatic support 
       for multiple subscribers for outgoing brokers 
    9. A PDF version of the HTML documentation (thanks to
       http://www.easysw.com and their open source conversion tool!)  

Changes from 3.0beta1 include: 

    1. Expanded availability of the new alternative Hub syntax 
    2. Elimination of all known memory leaks 
    3. Bug fixes 
    4. Improvements in Java documentation and upgrade notes 
    5. Better support for broker aborts, including updates to all
       audio examples  
    6. Improvements to PDF rendering of the HTML documentation 
    7. Expanded Hub debugging support, featuring an interactive loop to
       explore the Hub state  
    8. Final implementation of encapsulation of administrative
       information between Hub and server  
    9. Shortening of default poll increment from 100 ms to 5 ms 

We are continuing to test the infrastructure extensively, and will
release 3.0 final in the near future. There will be no feature
changes, modifications or enhancements between this beta and the final
release, only bug fixes. Please direct all bugs, as usual, to
bug...@li...; please do not send mail directly to
members of the Communicator team.

The GalaxyCommunicator 3.0beta2 distribution comes with extensive
documentation (see docs/index.html), a detailed list of new features
(see docs/new_features.html), and an upgrade guide for 2.1
installations to 3.0beta2 (see docs/3point0upgrade.html). Upgrade
assistance and guidance is also available at
bug...@li....

The GalaxyCommunicator 3.0beta2 release is an open source
distribution. It is available at http://fofoca.mitre.org/download.

Samuel Bayer 
For the Communicator team 

P.S. MIT Galaxy users: The MIT Galaxy system will not compile against
Galaxy Communicator 3.0beta2 without minor modifications.  MITRE has a
set of working patches, which you may contact me directly in order to
obtain.

[Communicator-user] ROAR RFI to be Posted

[jbass <jb...@da...>]

Dear Sam,

This is the last ROAR related announcement I will send through the
Communicator listserv.  So please let this one go, and I will build my own
list after I get the responses to the RFI

Jim


ASR Community:
NOTICE:  The ROAR RFI will be posted in the CBD on 4 January 2001.  The
request will be open for 30 days.  Note - I will NOT be able to discuss
technical issues after the document is posted.  However, the RFI is
self-explanatory.  Good luck.

Jim

[Communicator-user] Announcing Galaxy Communicator 3.0beta1

[Samuel L. B. <sa...@li...>]

All -

We are, as usual, pleased and relieved to announce the availability of
Galaxy Communicator 3.0beta1. Version 3.0 has been under development
since late summer, and this beta contains almost all the features
we'll have time to wedge into the 3.0 distribution. Even though the
internals of the infrastructure have changed in some major ways, the
upgrade from 2.1 to 3.0 will be quite simple for the great majority of
users. Version 3.0 features:

- Vastly improved tools for managing simultaneous sessions

- More flexible and robust Hub-server interaction, including the
  introduction of continuations and the elimination of deadlocks 

- Support for server location files, which help maintain consistent
  port location information across Hub and servers 

- Many infrastructure improvements, including cross-language support
  for distinguishing among Galaxy Communicator versions, improved
  timed task control, and a consistent, event-driven programming model
  for embedding the Galaxy Communicator library

- Improvements in the frame library, including support for dynamically
  expandable lists and arrays, better memory management options, and
  access to the full range of Communicator types as frame fills

- More flexibility in the Hub syntax and organization, including
  better management of servers and service types, new support for
  choosing among available servers, and an alternative syntax which
  provides a wider array of control options and eliminates some of the
  idiosyncracies in the default syntax 

- A completely revised communications protocol, including XDR encoding
  for all brokering and message traffic and better encapsulation of
  administrative information

- Significant brokering improvements, including access to the full
  range of Communicator types for brokering and automatic support for
  multiple subscribers for outgoing brokers

- A PDF version of the HTML documentation (thanks to
  http://www.easysw.com and their open source conversion tool!)

We anticipate a beta testing period of approximately one month, during
which we will make a few final enhancements and test the
infrastructure extensively. Please direct all bugs, as usual, to
bug...@li...; please do not send mail directly to
members of the Communicator team.

The GalaxyCommunicator 3.0beta1 distribution comes with extensive
documentation (see docs/index.html), a detailed list of new features
(see docs/new_features.html), and an upgrade guide for 2.1
installations to 3.0beta1 (see docs/3point0upgrade.html). 

The GalaxyCommunicator 3.0beta1 release is an open source
distribution. It is available at http://fofoca.mitre.org/download.

Samuel Bayer
For the Communicator team

P.S. MIT Galaxy users: The MIT Galaxy system will not compile against
Galaxy Communicator 3.0beta1 without minor modifications. MITRE has a
set of working patches, which we've forwarded to MIT for further
testing. We have not yet discussed with MIT which one of MIT or MITRE
will be supporting this upgrade. If you have questions, feel free to
contact me directly (sa...@mi...).

[Communicator-user] Announcing: Communicator Open Source workshop

[Samuel L. B. <sa...@li...>]

All -

CMU and the MITRE Corporation would like to invite DARPA Communicator
program participants to a workshop on open source
Communicator-compliant software.

WHEN: January 12, 2001
WHERE: CMU
AGENDA: exchange of plans for open source releases, discussion of
issues involving use and commercialization of open source,
presentation of "lessons learned"

This workshop is open to all DARPA Communicator program participants;
as long as you're interested in the issue of open source software for
dialogue systems and you feel you have something to contribute, you
don't need to be planning to offer such software to attend. The format
of the workshop will depend on its size, but will almost certainly
involve a mix of formal presentations and round-table discussions.

We currently have expressions of interest from MITRE, University of
Mississippi, Lockheed-Martin, and CMU. Other sites should respond
directly to me at sa...@mi... by December 15, 2000, to allow the CMU
folks time to make the appropriate local arrangements. We'll send
hotel recommendations, etc., to participants directly.

Cheers,
Samuel Bayer
The MITRE Corporation
sa...@mi...

[Communicator-user] Open source conference: repost

[Samuel L. B. <sa...@li...>]

All -

On 10/26, I sent out a request for interest in a Communicator open
source software workshop, to be held in January at CMU. My original
deadline for expressions of interest was this past Friday, November
10. I'd like to extend that deadline to this coming Friday, November
17. The original request is available at
http://www.geocrawler.com/archives/3/4380/2000/10/0/4559294/. 

Sam Bayer
The MITRE Corporation
sa...@mi...

[Communicator-user] Proposal for open source Communicator software workshop

[Samuel L. B. <sa...@li...>]

All -

At the September PI meeting, I raised the possibility of having a
workshop on open source Communicator software. Both CSLR and CMU
expressed immediate interest, and we've been corresponding about a
possible plan. Here's what we have so far:

Participants
------------

Our initial idea would be to open this workshop to anyone who has
released Communicator-compliant open source software or intends to in
the near future. If there's sufficient additional interest from people
who are interested in CONSUMING such software, we can reevaluate this
restriction. 

Dates
-----

Mid-January seems to be the most likely time. CMU proposes January
12. 

Duration
--------

We believe no more than a day would be needed. However, if there are
related issues which might be appropriate to discuss, we're open to
having a longer workshop (or a companion workshop on an adjacent
day). 

Location
--------

CMU has volunteered to host (thanks, Kevin Lenzo).

Agenda
------

At the moment, we have only seeds of ideas:

- Status of end-to-end open source Communicator system(s), including
  discussion of missing capabilities
- Discussion of different open source licensing options
- Discussion of "lessons learned" in licensing
- Review of message standardization efforts (possibly)

We're eager for more ideas.

Schedule
--------

If you're interested, please send email to me at sa...@mi... with
number of possible attendees, additional agenda items, whether you're
interested in actually giving a talk about any of the agenda items,
and possible problems with dates. In order to allow time to plan, I'd
like to collect all the inputs by COB Friday, November 10 (two weeks
from tomorrow). At that point, we can assess how to proceed.

Thanks for your attention -
Sam Bayer
The MITRE Corporation
sa...@mi...

[Communicator-user] ROAR Status

[jbass <jb...@da...>]

All,

Just to let everyone know, the pitch for ROAR was delayed until 3 Nov 2000.
We are primed, but I will keep my edge until the new presentation date.  I
will keep you all informed.  Please pass this information around the
community.

Jim

James D. Bass, Ph.D.
Lieutenant Colonel, United States Army
Program Manager - Information Technology Office
* * * * *
DARPA-ITO
3701 North Fairfax Drive
Arlington, VA 22203-1714
* * * * *
Office:  703.696.2227
Fax:  703.696.4534
SETA: Tracie Smith 703.522.6067, ext. 153 

[Communicator-user] sclite for win32?

[Sasha P. C. <sas...@sp...>]

Does anyone have a port of the nist scoring tools for Windows?

Thanks,

Sasha

[Communicator-user] Announcing the availability of patch 1 to GalaxyCommunicator 2.1

[Samuel L. B. <sa...@li...>]

All -

As I announced on Friday, there is a bug in the Hub in
GalaxyCommunicator 2.1 which causes some systems to manage session IDs
incorrectly. We have provided a patch to GalaxyCommunicator 2.1 which
addresses this problem by reinstating the previous behavior in the
appropriate circumstances. Both CMU and CSLR have installed versions
of this fix and report that their systems now run smoothly, and are
taking advantage of the greater reliability and better memory
management in the 2.1 Hub.

While this patch is adequate for current applications, there are a
number of significant questions about session management which are
currently not addressed by this fix (or in the previous
distributions). We will address these questions more thoroughly in the
upcoming 3.0 distribution.

In addition, we have included the updated log analysis tools which we
previously issued as a patch to GalaxyCommunicator 2.0.1. With this
2.1 patch, both distributions now have the most up-to-date log
analysis tools.

This patch is available in the open-source area at 

http://fofoca.mitre.org/download/index.html

This patch is available as a source-level patch for Unix, and
precompiled binaries for Windows NT are also provided. Note that the
previous 2.1 download for Windows NT linked to the incorrect file;
this problem has also been fixed.

Please report all bugs, as usual, to bug...@li.... 

Sam Bayer
for the Communicator team

[Communicator-user] FW: Welcome to the "Communicator-user" mailing list

[Allen S. <as...@cn...>]

Please post me.  pw: MtSO

allen

-----Original Message-----
From: com...@li...
[mailto:com...@li...]On Behalf Of
com...@li...
Sent: Saturday, September 30, 2000 2:47 PM
To: as...@cn...
Subject: Welcome to the "Communicator-user" mailing list

Welcome to the Com...@li... mailing list!

To post to this list, send your email to:

  com...@li...

General information about the mailing list is at:

  http://lists.sourceforge.net/mailman/listinfo/communicator-user

If you ever want to unsubscribe or change your options (eg, switch to
or from digest mode, change your password, etc.), visit your
subscription page at:


http://lists.sourceforge.net/mailman/options/communicator-user/asears@cnri.r
eston.va.us


You can also make such adjustments via email by sending a message to:

  Com...@li...

with the word `help' in the subject or body (don't include the
quotes), and you will get back a message with instructions.

You must know your password to change your options (including changing
the password, itself) or to unsubscribe.  It is:

  MtSO

If you forget your password, don't worry, you will receive a monthly
reminder telling you what all your lists.sourceforge.net mailing list
passwords are, and how to unsubscribe or change your options.  There
is also a button on your options page that will email your current
password to you.

You may also have your password mailed to you automatically off of the
Web page noted above.

[Communicator-user] Re: Communicator-user -- confirmation of subscription -- request 827753

[David H. <dh...@vi...>]

confirm 827753

[Communicator-user] is the list initialized??

[John A. <abe...@mi...>]

yes?