unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marc Manthey <marc@let.de>
Cc: saf <saf@xy1.org>, Richard Stallman <rms@gnu.org>,
	Ricardo Barbosa <rbarbosa@ulb.ac.be>,
	Karl Berry <karl@freefriends.org>
Subject: CUSeeMe Source Code - Zaheer Shamsi urgent please read this !!!
Date: Sat, 28 May 2005 00:14:37 +0200	[thread overview]
Message-ID: <84BFB73E-056B-4C82-A48D-67C811F18A2C@let.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2043 bytes --]


gentlemen .

i need  to get in cotact with this  guy he  has the  cornell code for  
cuseeme.!!!!
************************************************************************ 
**************************
Zaheer Shamsi (zaheer@rindu.enemy.org)
Wed, 29 Apr 1998 02:27:21 +0800 (MYT)

Environment: Win95, Visual C++ 5, ATM network
Hi !

This is a repeat query, pls. response.

We are working on developement of video conferencing application on ATM
network at our University. We have obtained the CUSeeMe source code to
study the techniques/logic used.

Unfortunatly, I'm not an expert on Visual C++, the proposed developing
plateform, so I need soem guidance in understanding the control flow of
the mentioned source code.

I suggest, if possible, that Cornell people should include another  
readme file
in the package describing, how to build the CUSeeMe application from  
this code,
how one can reach the appropriate part of the code for a specific  
features
like:-

* how video/voice format is captured.
* how these data parts are sent and synchronised.
* which part is doing the compression, etc.

P.S. bear with me if things not expressed appropriatly.



i need  to get in contact with  Zaheer Shamsi

regards
http://baby.indstate.edu/CU-SeeMe/devl_archives/apr_98/0169.html
http://baby.indstate.edu/CU-SeeMe/devl_archives/apr_98/0081.html

> From: Richard Stallman <rms@gnu.org>
> Date: May 8, 2005 11:03:30 AM GMT+02:00
> To: Marc Manthey <marc@let.de>
> Cc: karl@freefriends.org
> Subject: Re: free cuseeme 0.7 ?
> Reply-To: rms@gnu.org
>
>
>     sorry i mean that version  .80 is  NOT free because of the
>     PLUGin  funktionallity  that arron glles developed and  
> implemented.
>
> The information sent to me seems to say that essentially ALL of
> version .80 was non-free.  I don't see how the license change relates
> to plug-in functionality.  Perhaps there is some relationship I do not
> see.  If so, could you explain the relationship more clearly?
>
> Meanwhile, I will contact people at Cornell to look for version .70.




[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2814 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

                 reply	other threads:[~2005-05-27 22:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84BFB73E-056B-4C82-A48D-67C811F18A2C@let.de \
    --to=marc@let.de \
    --cc=karl@freefriends.org \
    --cc=rbarbosa@ulb.ac.be \
    --cc=rms@gnu.org \
    --cc=saf@xy1.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).