Re: CUSeeMe Web app for the Mac

Jay Ashcraft (
Thu, 29 Jun 1995 15:01:10 -0500 wrote:

:White Pine Software, Inc. demo'd a pre-release version of
:CU-SeeMe/Macintosh at the DVC show out west a month or so ago which has the
:below mentioned capabilities.
:It used a CU-SeeMe config. file which contained a reflector's IP address
:and an ID #.
:The web server needed to have a new mime type added to it (CUSeeMe specific).
:The web browser needed to be configured to have CU-SeeMe be a helper app..
:The user needed to create a link in their web page to the CU-SeeMe config.

:When selecting the link within the web page, the web browser would start up
:CU-SeeMe and CU-SeeMe would "process" the CU-SeeMe config file received
:from the web server and then automatically connect to the reflector

I add to the bandwidth:)

There are examples of these links to the KVR-InterneTV Reflectors and an
example of a Apple QTC web link at:

Actually at /tstvframe2.html as the previous link links to the second page
link after a Netscape animation.

I don't know if the CU-SeeMe links (noted as IP #'s will work with the
windoze versions but they use the same syntax as the original stab Web
links that Cornell and WP used at their announcement.

I haven't done a GOCU-SeeMe link yet.

I believe I am using application/x-cuseeme (mimetype/subtype) with the
extension .cu which in Netscape is set to launch. Of course it can work for
the developers at White Pine and Cornell but for others about all it will
do is open CU-SeeMe, then you can go back to the web page select and copy
go back to CU-SeeMe and enter comand K and take the mouse and mouse paste
and hit enter, but it would be cool to also deselect send as our
reflectors request receive only and at higher speeds (not modems:)

The QTC link is only experimental cause I can't get QTC and CU-SeeMe to
share Quicktime and the spigot:)

Perhaps there is a way to write a script or a macro program that takes a
mime-type/subtype from a link that opens a script and CU-SeeMe and
physically mouse pastes and hits enter. Otherwise we wait, after all this
is a public massively tested beta software which we all should be

The downside and unanswered question is the the WP Web states that the WP
version will be web linkable but that the Cornell version won't. It is my
recall that Dick said that another alpha or beta version for the Mac would
be released in a few weeks many weeks ago, but that was before the WP
announcement and they have been working many hours a day to get the
reflectors to work with varying speeds at the same time. Dick also
inferred that linking to the web would be included. Cornell is doing much
and priorites rule. I am not bitching or attemping to take time away from
coding, just posing the question again four months later for clarification.
I can understand the issues and the rationale . . .

Bill at WP's adds:

;The how to do it is the easy part. The hard part is agreeing on a
;connection file format. We'd like to do it right the first time. One of the
;topics being discussed is to use a URL definition for nicknames. This
;requires involving many people from various companies and thus takes awhile
;(inorder to define a VC type URL). Seeing as the connection file would need
;to contain the URL, the URL definition holds things up.

;The connection file could just be IP based for now, and we could keep
;backwords compatability once a URL is defined. This is being considered by

. . . but on the otherside more unofficial hacks will evolve as with
GOCU-SeeMe and CU-WelcomeMat This takes away from Cornell and WP to set
the standards. I also remember that some of the earlier versions allowed
comand k comand v to paste. Perhaps the newer versions will support this

I can understand Cornell and WP's priorities and Cornell's needs.
Priorities such as bandwidth optimization for varying speeds of users and
the reflectors, an API for add ons, etc. interoperability between
platforms and versions (Cornell's, WP's). Perhaps using QTC too.

Dick today states that "launch-docs for web support" are a medium term
priority. I again assume that he speaks for the Cornell version but he
makes no reference to if it will be in the alpha release in the next few
days or the beta to follow.

Dick said:
;We expect further releases later in July: for the Mac with a new
;participants list, improved audio control panel, and working QuickCam
;audio; for Windows with audio send and similar audio control panel and
;participant list.

Reflector optimization is indeed quite a priorty and a challege. It is
difficult to do everything at once without funding, human resources. I
live this everyday myself, I understand and wish I could contribute $$ but
I can't . . .as I tell my fellow workers "all good things in good time" It
is a process. One step at a time.

In so far as mime-types many HTTPD programs still call aiff x-aiff
but aiff is pretty standard audio format on the mac platform. In so far as
incorporating URL standards, that Will take time but experimental types can
lead to accepted standards. If WP and Cornell don't do it then others will
try and make hacks to it as it is a natural path in these times.

Other longer term issues would be Interoperability with the QTC extention
and OT. How will QTC
work with either WP's or Cornell's applications? Some argue in the press
that WP and Apple are in competition but after all QTC is just an
extension, just like quicktime. The words I here from some unnamed sources
is that QTC will work with CU-SeeMe.

With the spirit of love and proactive productive public discourse to all,
(not bitching)

Jay Ashcraft, Program Director