RE: [twsocket] VOIP
Have you looked into what kind of effort it take to accomplish this? I might be interesting of helping out a bit. I have done a lot of TAPI programming and know a bit about that. I have played little with VOIP but I it might be interesting to take a closer look again. Regards, Fredrik. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arno Garrels Sent: Tuesday, April 26, 2005 11:18 AM To: ICS support mailing Subject: Re: [twsocket] VOIP I've just found something interisting here: http://www.ictrnid.org.uk/downloads/SIP/SIP-0.3.zip The stack uses Indy 9.0.14 :( why not ICS? RNID SIP STACK == This library of code consists of three main parts: * a SIP stack (RFC 3261), * an RTP stack (RFC 3550), and * SDP (RFC 2327) parsing and utilities. The code currently implements most of SIP, RTP. The stack can make and receive calls from/to X-Lite, linphonec. It also connects correctly with ser, the Sip Express Router. Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] VOIP
Fredrik Larsson wrote: Have you looked into what kind of effort it take to accomplish this? From the first view, and having read just 30% of RFC3261 it's nothing you could do just on the fly. However SIP appears to be an easy to learn protocol. I'm not sure if implementing VOIP with ICS makes sense due to missing SSL support, which isn't required but a feature. I've also read somewhere about SMIME. Looking at the huge units of the RNID SIP STACK I'm actually a bit frustrated :( but that may change, I need to read and understand more RFC's, I'm just playing with the idea. I might be interesting of helping out a bit. I have done a lot of TAPI programming and know a bit about that. I have played little with VOIP but I it might be interesting to take a closer look again. Regards, Fredrik. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arno Garrels Sent: Tuesday, April 26, 2005 11:18 AM To: ICS support mailing Subject: Re: [twsocket] VOIP I've just found something interisting here: http://www.ictrnid.org.uk/downloads/SIP/SIP-0.3.zip The stack uses Indy 9.0.14 :( why not ICS? RNID SIP STACK == This library of code consists of three main parts: * a SIP stack (RFC 3261), * an RTP stack (RFC 3550), and * SDP (RFC 2327) parsing and utilities. The code currently implements most of SIP, RTP. The stack can make and receive calls from/to X-Lite, linphonec. It also connects correctly with ser, the Sip Express Router. Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] [HELP] FtpServer : Long Process HOWTO
Thanks for your answer François. yep... that's what i was supposing. meaning that if the making of such a file in the event handler take some time (10 s let's say), and i have 10 clients asking almost simultaneously for images, the last one will have to wait for 100 secs before receiving anything. Better then to send files one by one... even if there're 1200+ images... else someone has another idea ? knowing that all the images are stored in a db and retrieved on demand. best regards, FTP server component will send the files simultaneously to all client at their own speed. It is serialized only when in the event handler, not for sending files. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Guillaume MAISON [EMAIL PROTECTED] To: iCS support mailing twsocket@elists.org Sent: Tuesday, April 26, 2005 5:10 PM Subject: [twsocket] [HELP] FtpServer : Long Process HOWTO Hi everyone, here's my problem : still in my video server, i'm using the FtpServer component to download a set of images, taken from a camera, through one simple RETR call. On the OnGetProcessing event, i retrieve from a DB (the connection has already been made) all the images needed (range of images provided in the filename which is formatted) and push them into the Client.Datastream. for the algorithm, i have no problem. but what happens if several ftp client asks at the same time for a big amount of images (average : 1 image = 21Ko) let's say 1200 images ? Is Each OnGetProcessingEvent fired one after anoher ? which would then result in a queueing of each request... thanks for your help ! Best regards, Guillaume MAISON - Guillaume MAISON - [EMAIL PROTECTED] 83, Cours Victor Hugo 47000 AGEN Tél : 05 53 87 91 48 - Fax : 05 53 68 73 50 e-mail : [EMAIL PROTECTED] - Web : http://nauteus.com -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be Guillaume MAISON - Guillaume MAISON - [EMAIL PROTECTED] 83, Cours Victor Hugo 47000 AGEN Tél : 05 53 87 91 48 - Fax : 05 53 68 73 50 e-mail : [EMAIL PROTECTED] - Web : http://nauteus.com -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] [HELP] FtpServer : Long Process HOWTO
meaning that if the making of such a file in the event handler take some time (10 s let's say), and i have 10 clients asking almost simultaneously for images, the last one will have to wait for 100 secs before receiving anything. You you have to hang into the event handler for 10 seconds, then you have a problem. You should redesign your code as an asynchronous operation, probably using threads. else someone has another idea ? knowing that all the images are stored in a db and retrieved on demand. You don't need to have to wait 10 seconds to get the image from the DB ! Or if really you have, then use another DBMS. -- [EMAIL PROTECTED] http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Overwriting of HttpCli properties
Hello, while I'm working on the fix for the authentication I would like to remove one think that I don't like. The component will overwrite the Username and Password properties when an user and a password is specified in the url. The problem is that when the user set another url without user and password then the properties mantains the values specified in the previous url. This will mean that it is possible that these values could be sent to the wrong server, and if a basic authentication is used, it could be a security issue. I would like to change this behaviour in the following way. The user will be get from url if present, otherwise from the Username property. The same for the password. The properties will be not changed anymore. Before doing this I want to hear the opinion of all developers that are in this mailing list, in particular if there are good reasons to do not apply these changes. The same logic will apply to Connection and ProxyConnection, but it's overwriting appeared very recently, so I don't think that it will break any existing code. More probably is true the opposite. Bye, Maurizio. This mail has been sent using Alpikom webmail system http://www.alpikom.it -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
RE: [twsocket] Overwriting of HttpCli properties
Hello, In my oppinion username and(or) passwords in the url are really useless to implement. Think about Internet Explorer which inhibed this also. Also, how can you specify proxy credentials in the url? regards -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maurizio Lotauro Sent: Wednesday, April 27, 2005 7:11 PM To: ICS support mailing Subject: [twsocket] Overwriting of HttpCli properties Hello, while I'm working on the fix for the authentication I would like to remove one think that I don't like. The component will overwrite the Username and Password properties when an user and a password is specified in the url. The problem is that when the user set another url without user and password then the properties mantains the values specified in the previous url. This will mean that it is possible that these values could be sent to the wrong server, and if a basic authentication is used, it could be a security issue. I would like to change this behaviour in the following way. The user will be get from url if present, otherwise from the Username property. The same for the password. The properties will be not changed anymore. Before doing this I want to hear the opinion of all developers that are in this mailing list, in particular if there are good reasons to do not apply these changes. The same logic will apply to Connection and ProxyConnection, but it's overwriting appeared very recently, so I don't think that it will break any existing code. More probably is true the opposite. Bye, Maurizio. This mail has been sent using Alpikom webmail system http://www.alpikom.it -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
RE: [twsocket] Overwriting of HttpCli properties
Scrive Tibor Csonka [EMAIL PROTECTED]: Hello, In my oppinion username and(or) passwords in the url are really useless to implement. Think about Internet Explorer which inhibed this also. It is already implemented so since long time, and I think this is not limited to the http url. Removing it is a different question from my. Any discussion about that is wellcome. Also, how can you specify proxy credentials in the url? Actually you can't. Bye, Maurizio. This mail has been sent using Alpikom webmail system http://www.alpikom.it -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
