Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING
I think the problem goes to TCustomWSocket. Its methods must also be renamed if we decide to follow that route... Regards, SZ - Original Message - From: Bjørnar Nielsen [EMAIL PROTECTED] To: 'ICS support mailing' twsocket@elists.org Sent: Tuesday, June 26, 2007 2:54 PM Subject: Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING I'm not sure renaming would solve the problem. If I remember correctly, I tried to rename SendTo and 2 Send-procedures (I think it was one for sending just a byte and another for sending more data) in the Httpclient-class. You could try it also, maybe you could get it to work, I could not (I don't have much experience coding Delphi). Regards Bjørnar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fastream Technologies Sent: 26. juni 2007 12:52 To: ICS support mailing Subject: Re: [twsocket] [ICS-SSL] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITY WARNING Hint: I think the problem must be related with BCB making Delphi namespaces flat--global. IOW, the send and sendto in OverbyteIcsWinsock clashes with those in wsocket.pas. Not in delphi because they are in distinct separate namespaces in delphi but in BCB. As I said, renaming may be a solution, but a lot painful since would break compatibility. Bjornar, What do you think? Agree? Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, June 26, 2007 1:25 PM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITY WARNING Sorry. Since the problem occurs with THttpServer, I think I should post to twsocket but can we assume all of the members of ics-ssl are also members of twsocket? Also, will you (Francois) be debugging the problem? I created the most simple test case for you as you always want us to do... We can pay for it. I wrote this as well but you said nothing about that.. Best Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: SSL implementation for ICS [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Sent: Tuesday, June 26, 2007 12:49 PM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 availableBCB2006COMPATIBILITYWARNING Please stop spamming the lists and myself. Use only one mailing list, the best suited for your problem. If you annoy please, they won't help you. Remember we have only volunteers here. No one is paid to answer your questions. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Cc: Francois PIETTE [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:10 AM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING Sorry it ought to be http://www.fastream.com/ics/LinkerBugTest.zip instead. Best Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Cc: Francois PIETTE [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:34 AM Subject: Re: New ICS-V6 andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING Hello, I have been able to reproduce the error with a 10-lines HTTP server demo in BCB2006. Here it is: http://www.fastream.com/ics/LinkerBugTester.zip . It does not link! Francois, please help us fix this as it seems that Fastream is not the only company suffering from this in ALL (both SSL and normal) V6 under BCB6-2006. You can count this for our consultancy budget. Best Regards, SZ - Original Message - From: Bjørnar Nielsen [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 10:28 AM Subject: Re: [ICS-SSL] [twsocket] New ICS-V6 andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING I had this problem myself when deriving the client-component in the webserver. I'm just guessing here that you have a project similar to the webserver. The problem was that I could not use C++ to derive the client-component, I had to implement the derived class I Delphi. I never found another workaround. By the way, I use BCB Pro 6.0. I'm not sure if it's related to SSL or not. I got this problem when switching to ICS V6. Regards Bjørnar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fastream Technologies Sent: 25. juni 2007 20:35 To: SSL implementation for ICS Subject: Re: [ICS-SSL] [twsocket] New ICS-V6 and ICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING I do not think it is a SSL problem. I saw this with versions prior to ICS-SSL! - Original Message - From: Francois PIETTE [EMAIL PROTECTED] To: ICS support mailing twsocket
Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING
I am 99% sure it is a name clash now. I hope somebody profficient in Delphi can look to my demo. BTW, can you see the same error with my demo project? Regards, Gorkem - Original Message - From: Bjørnar Nielsen [EMAIL PROTECTED] To: 'ICS support mailing' twsocket@elists.org Sent: Tuesday, June 26, 2007 2:54 PM Subject: Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING I'm not sure renaming would solve the problem. If I remember correctly, I tried to rename SendTo and 2 Send-procedures (I think it was one for sending just a byte and another for sending more data) in the Httpclient-class. You could try it also, maybe you could get it to work, I could not (I don't have much experience coding Delphi). Regards Bjørnar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fastream Technologies Sent: 26. juni 2007 12:52 To: ICS support mailing Subject: Re: [twsocket] [ICS-SSL] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITY WARNING Hint: I think the problem must be related with BCB making Delphi namespaces flat--global. IOW, the send and sendto in OverbyteIcsWinsock clashes with those in wsocket.pas. Not in delphi because they are in distinct separate namespaces in delphi but in BCB. As I said, renaming may be a solution, but a lot painful since would break compatibility. Bjornar, What do you think? Agree? Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, June 26, 2007 1:25 PM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITY WARNING Sorry. Since the problem occurs with THttpServer, I think I should post to twsocket but can we assume all of the members of ics-ssl are also members of twsocket? Also, will you (Francois) be debugging the problem? I created the most simple test case for you as you always want us to do... We can pay for it. I wrote this as well but you said nothing about that.. Best Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: SSL implementation for ICS [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Sent: Tuesday, June 26, 2007 12:49 PM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 availableBCB2006COMPATIBILITYWARNING Please stop spamming the lists and myself. Use only one mailing list, the best suited for your problem. If you annoy please, they won't help you. Remember we have only volunteers here. No one is paid to answer your questions. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Cc: Francois PIETTE [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:10 AM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING Sorry it ought to be http://www.fastream.com/ics/LinkerBugTest.zip instead. Best Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Cc: Francois PIETTE [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:34 AM Subject: Re: New ICS-V6 andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING Hello, I have been able to reproduce the error with a 10-lines HTTP server demo in BCB2006. Here it is: http://www.fastream.com/ics/LinkerBugTester.zip . It does not link! Francois, please help us fix this as it seems that Fastream is not the only company suffering from this in ALL (both SSL and normal) V6 under BCB6-2006. You can count this for our consultancy budget. Best Regards, SZ - Original Message - From: Bjørnar Nielsen [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 10:28 AM Subject: Re: [ICS-SSL] [twsocket] New ICS-V6 andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING I had this problem myself when deriving the client-component in the webserver. I'm just guessing here that you have a project similar to the webserver. The problem was that I could not use C++ to derive the client-component, I had to implement the derived class I Delphi. I never found another workaround. By the way, I use BCB Pro 6.0. I'm not sure if it's related to SSL or not. I got this problem when switching to ICS V6. Regards Bjørnar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fastream Technologies Sent: 25. juni 2007 20:35 To: SSL implementation for ICS Subject: Re: [ICS-SSL] [twsocket] New ICS-V6 and ICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING I do not think it is a SSL problem. I saw this with versions prior to ICS-SSL! - Original Message - From: Francois PIETTE [EMAIL
Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING
I don't have time to test you project, but I looked at the source, and I got my error the same way, but the difference was that I also had to call the send-method to trigger the linker-error. The combination of calling send and setting classid made this error trigger. Regards Bjørnar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fastream Technologies Sent: 26. juni 2007 15:49 To: ICS support mailing Subject: Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING I am 99% sure it is a name clash now. I hope somebody profficient in Delphi can look to my demo. BTW, can you see the same error with my demo project? Regards, Gorkem - Original Message - From: Bjørnar Nielsen [EMAIL PROTECTED] To: 'ICS support mailing' twsocket@elists.org Sent: Tuesday, June 26, 2007 2:54 PM Subject: Re: [twsocket] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITYWARNING I'm not sure renaming would solve the problem. If I remember correctly, I tried to rename SendTo and 2 Send-procedures (I think it was one for sending just a byte and another for sending more data) in the Httpclient-class. You could try it also, maybe you could get it to work, I could not (I don't have much experience coding Delphi). Regards Bjørnar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fastream Technologies Sent: 26. juni 2007 12:52 To: ICS support mailing Subject: Re: [twsocket] [ICS-SSL] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITY WARNING Hint: I think the problem must be related with BCB making Delphi namespaces flat--global. IOW, the send and sendto in OverbyteIcsWinsock clashes with those in wsocket.pas. Not in delphi because they are in distinct separate namespaces in delphi but in BCB. As I said, renaming may be a solution, but a lot painful since would break compatibility. Bjornar, What do you think? Agree? Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Tuesday, June 26, 2007 1:25 PM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 available BCB COMPATIBILITY WARNING Sorry. Since the problem occurs with THttpServer, I think I should post to twsocket but can we assume all of the members of ics-ssl are also members of twsocket? Also, will you (Francois) be debugging the problem? I created the most simple test case for you as you always want us to do... We can pay for it. I wrote this as well but you said nothing about that.. Best Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: SSL implementation for ICS [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Sent: Tuesday, June 26, 2007 12:49 PM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 availableBCB2006COMPATIBILITYWARNING Please stop spamming the lists and myself. Use only one mailing list, the best suited for your problem. If you annoy please, they won't help you. Remember we have only volunteers here. No one is paid to answer your questions. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Cc: Francois PIETTE [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:10 AM Subject: Re: [ICS-SSL] New ICS-V6andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING Sorry it ought to be http://www.fastream.com/ics/LinkerBugTest.zip instead. Best Regards, SZ - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED]; ICS support mailing twsocket@elists.org Cc: Francois PIETTE [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:34 AM Subject: Re: New ICS-V6 andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING Hello, I have been able to reproduce the error with a 10-lines HTTP server demo in BCB2006. Here it is: http://www.fastream.com/ics/LinkerBugTester.zip . It does not link! Francois, please help us fix this as it seems that Fastream is not the only company suffering from this in ALL (both SSL and normal) V6 under BCB6-2006. You can count this for our consultancy budget. Best Regards, SZ - Original Message - From: Bjørnar Nielsen [EMAIL PROTECTED] To: 'SSL implementation for ICS' [EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 10:28 AM Subject: Re: [ICS-SSL] [twsocket] New ICS-V6 andICS-SSL-V6 availableBCB2006COMPATIBILITY WARNING I had this problem myself when deriving the client-component in the webserver. I'm just guessing here that you have a project similar to the webserver. The problem was that I could not use C++ to derive the client-component, I had to implement the derived class I Delphi. I never found another workaround. By the way, I use BCB Pro 6.0. I'm not sure if it's
