On Mon, 01 May 2006 13:37:04 -0400, Philippe Khalaf <[EMAIL PROTECTED]> wrote:

On Sun, 30 Apr 2006 13:44:19 -0400
"Youness Alaoui" <[EMAIL PROTECTED]> wrote:

we connect to the reflector and get the information from there and send it
to farsight (yes, done in the beggining, just as MSN does)
we then ask farsight to 'prepare_transports', once they are ready (known
through a callback), we then get information on ourself with farsight api,
and build the outgoing xml (this step could be done in the beggining
depending on who needs to send the xml first, you or the other user)...
this should take care of any upnp, nat traversal stuff, open the ports,
etc...
I think the reflector part should be implemented inside the msnwebcam
farsight plugin. It never got around to implementing it when I
originally wrote the plugin.


no, the reflector part should be done in amsn I think, because it's part of the protocol, you need the address of the reflector, you need HTTP requests (want to include an http lib in farsight?) to create your tunnel and session, AND you need to send (or receive) the reflector information/identification from the SB, so it's anyways a part of the work that has to be done from amsn (since it's msnp2p protocol), so let it all be done from amsn, and be send as a connection candidate that will only be used if the timeout is reached. If you have other arguments to convince me, tell me.

Also for uPnP, it can/should also be done from inside Farsight. I'm
planning on releasing a uPnP wrapper in Farsight core soon that uses
clinkc for uPnP.


cool, how is your progress with that ? I still need to finish my work to remove the sofiasip/libjingle/gnet dependency, unless something else is used, but anyways, it's there for unix, the windows part, I know how to do it, I just need to do the code and test...
tell me when upnp is done so I can use your utils too and make it use that!

anyways, that's your call...
if you want to do only protocol stuff, then I can send you what I have on farsight, so you can continue my work (until next week I guess), the code is almost done being ported to the new API (spent 3 days on it, maybe only 1 or 2 days left of work), then we'll need to have a farsight-tcl package
that would wrap all farsight functions to be available from tcl directly
(maybe one more day of work), and finally, amsn needs to have calls to
farsight-tcl...
I promise I will try to get the wrapper I had if my old HDD isn't toast.

thanks! :)

btw, I just explained to Harry over msn how farsight works and now he's doing a design that should take farsight into consideration.


Regards,
Philippe

if we do this, we'll be good! webcam support will be much more easier this
way...
what do you think ?

KaKaRoTo



On Sun, 30 Apr 2006 06:42:21 -0400, Harry Vennik <[EMAIL PROTECTED]>
wrote:

> Ok, I will have a look at Farsight documentation to make sure that what
> I do
> will not be contrary to the way Farsight works. I already thought of a
> good
> frontend/backend separation and (for sending webcam) separation of the
> grabbing and the sending over the network. I don't think waiting for
> Farsight
> to be implemented is the perfect idea, I just need to keep Farsight in
> mind,
> and make my design such that Farsight can easily be used as a backend.
> Anyway, thanks for mentioning, I heard of it before, but did not think
> of it
> now!
>
> About multiple sources... in what I currently have there can be only one > source at a time. So you choose device for amsn, not per webcam session.
> And
> I think selecting it per session does not really have great advantages,
> and
> will make things unnecessarily more complex, both in development and
> use. But
> if others see advantages in being able to send from one device to one
> contact, and from another device to another contact, I can make it that
> way.
>
> What I currently have in the new code (partially), is most similar to the > approach we already had on Mac. Have 1 grabber window, and use the image
> from
> that grabber. It appeared most intuitive to me. Seeing myself on any
> webcam-related window I open (except receiving cam from others of
> course), is
> not necessary, seeing the image just once will do perfectly.
>
> If we allow multiple sources, we may have a grabber window for every
> source in
> use, so that isn't even a big change. (Or maybe better... for every
> source a
> tab... unless people really want to see multiple sources. hmmm....
> detachable
> tabs maybe??)
>
> Okay, just let me know what you all think, and I will try to conform to
> your
> wishes as much as possible ;-)
>
> Harry
>
> Op zondag 30 april 2006 11:21, schreef Philippe Valembois - Phil:
>> Really good idea !!
>> Some time ago I tried to clean up the code and make it clearer.... but I
>> gave up by lack of time...
>> Anyway, I would be happy if you would implement what I had in mind...
>> Currently we can send a preregistered session using a debug hack and it
>> applies to all open webcams... I wanted to generalize the way to grab
>> images... I mean, for each webcam session we could select the source of
>> the
>> image : either a file, a v4l device for linux, a DirectShow device for >> Windows and so on and make it in a way to be able to add easily another
>> device class (we never know)...
>> If you could do in a such way, it could be great !! :d
>> Phil
>> P.S. I just remind, Youness tried to implement Farsight in aMsn so maybe
>> you should wait for it since it should make the webcam management
>> easier...
>> I leave my mail content anyway since it can bring some ideas for future
>> development ;)
>> But if I understood well, Farsight is to use with gstreamer... And
>> gstreamer will be really powerful to let us do the things I exposed
>> above...
>>
>> Le Sunday 30 April 2006 08:23, Harry Vennik a écrit :
>> > Hi all,
>> >
>> > Just for your information, I started a msncam.tcl rewrite yesterday. >> > Karel told me about a memleak in it (objects array) and I thought it
>> > would be fairly simple to fix, but while investigating it, I found
>> many
>> > other things that slow the whole thing down, and also it was hard to
>> tell
>> > how to clean up the objects array (i.e. where to do a unset, and what
>> to
>> > unset then). So I had to draw the conclusion that starting from
>> scratch
>> > would be the best way to go. Of course I also copy/paste many code
>> from
>> > the current msncam.tcl, but most of it will be modified. For example,
>> the
>> > objects array will not exist anymore. I am using snit-objects for
>> > everything.
>> >
>> > Of course the rewritten msncam.tcl will not go into the 0.96 release,
>> but
>> > will get in cvs shortly after the release, so it can be thoroughly
>> tested
>> > before it gets into a release.
>> >
>> > I am monitoring all work on the current msncam.tcl to make sure I port >> > those changes to my new version if they apply to something that is in
>> > there already, but big code-reorganisations will be double work, so
>> > please don't bother ;-) We're in a bugfix-contest-before-release
>> anyway.
>> >
>> > Regards,
>> >
>> > Harry
>> >
>> >
>> > -------------------------------------------------------
>> > Using Tomcat but need to do more? Need to support web services,
>> security?
>> > Get stuff done quickly with pre-integrated technology to make your job
>> > easier Download IBM WebSphere Application Server v.1.0.1 based on
>> Apache
>> > Geronimo
>> >
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> > _______________________________________________
>> > Amsn-devel mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/amsn-devel
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services,
>> security?
>> Get stuff done quickly with pre-integrated technology to make your job >> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
>> _______________________________________________
>> Amsn-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
> _______________________________________________
> Amsn-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/amsn-devel



--
KaKaRoTo


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel



--
KaKaRoTo


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to