Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
14 to 15 asycnClick
#11
(05-04-2021, 02:20 AM)Alexandre Machado Wrote: I'll have a look and get back to you.

Thanks for the test case
Hi Alex, did you get a chance to look on it please?
Reply
#12
(05-10-2021, 07:12 AM)pgnair Wrote:
(05-04-2021, 02:20 AM)Alexandre Machado Wrote: I'll have a look and get back to you.

Thanks for the test case
Hi Alex, did you get a chance to look on it please?

Yes, I tested it. There is a bug in TMS code. I have no idea if they will ever fix it, so I'm fixing it myself.

BTW, why do you need this label control? It does nothing that our standard TIWLabel doesn't do already.

Here is how you fix it:

1) Open file IWTMSCtrls.pas

2) Find method TTIWHTMLLabel.RenderHTML

3) Comment out everything except the inherited call to it's ancestor method. Here's how it will be after it:

Code:
function TTIWHTMLLabel.RenderHTML(AContext: TIWBaseComponentContext): TIWHTMLTag;
//var
//  ajaxcall: string;
begin

//  if Assigned(OnAsyncClick) then
//    ajaxcall := 'processAjaxEvent(''onClick'', '
//      + HTMLControlImplementation.IWCLName
//      + ',''' + HTMLName + '.' + 'DoOnAsyncClick' + ''','
//      + 'true' + ', null, '
//      + 'true' + ');';

  Result := inherited RenderHTML(AContext);
//  Result.AddStringParam('onclick', ajaxcall);
end;

I'll add this to our (now long) list of fixes to TMS controls I did myself.

Build your application and run it. It will then work as expected.

Cheers
Reply
#13
(05-15-2021, 01:26 PM)Alexandre Machado Wrote:
(05-10-2021, 07:12 AM)pgnair Wrote:
(05-04-2021, 02:20 AM)Alexandre Machado Wrote: I'll have a look and get back to you.

Thanks for the test case
Hi Alex, did you get a chance to look on it please?

Yes, I tested it. There is a bug in TMS code. I have no idea if they will ever fix it, so I'm fixing it myself.

BTW, why do you need this label control? It does nothing that our standard TIWLabel doesn't do already.

Here is how you fix it:

1) Open file IWTMSCtrls.pas

2) Find method TTIWHTMLLabel.RenderHTML

3) Comment out everything except the inherited call to it's ancestor method. Here's how it will be after it:

Code:
function TTIWHTMLLabel.RenderHTML(AContext: TIWBaseComponentContext): TIWHTMLTag;
//var
//  ajaxcall: string;
begin

//  if Assigned(OnAsyncClick) then
//    ajaxcall := 'processAjaxEvent(''onClick'', '
//      + HTMLControlImplementation.IWCLName
//      + ',''' + HTMLName + '.' + 'DoOnAsyncClick' + ''','
//      + 'true' + ', null, '
//      + 'true' + ');';

  Result := inherited RenderHTML(AContext);
//  Result.AddStringParam('onclick', ajaxcall);
end;

I'll add this to our (now long) list of fixes to TMS controls I did myself.

Build your application and run it. It will then work as expected.

Cheers
Thanks a lot Alex, it is working properly now. You are great.
Reply
#14
You're welcome!
Thanks for your support :-)
Reply
#15
(05-19-2021, 01:12 AM)Alexandre Machado Wrote: You're welcome!
Thanks for your support :-)

One of the application successfully migrated to the version 15 and working fine in the Indy mode.

After that I converted it into Http.sys, and working fine in the non secure mode(http) but in secure mode it is not working. Getting 'page not not found' error in IE and ''Proxy error - Error during SSL handshake with remote server' in the chrome'. Any other changes is required in the application/firewall/network to get it work please?
Reply
#16
HTTP.sys and SA have different procedures to enable SSL.

https://blog.boxofbolts.com/ssl/windows/...d-windows/
Reply
#17
(05-23-2021, 06:28 PM)kudzu Wrote: HTTP.sys and SA have different procedures to enable SSL.

https://blog.boxofbolts.com/ssl/windows/...d-windows/

Thank you. It is working now. Awaiting responds from the client
Reply
#18
(05-25-2021, 01:41 AM)pgnair Wrote:
(05-23-2021, 06:28 PM)kudzu Wrote: HTTP.sys and SA have different procedures to enable SSL.

https://blog.boxofbolts.com/ssl/windows/...d-windows/

Thank you. It is working now. Awaiting responds from the client

Client reported slowness issue on SYS mode so rollbacked to the Indy mode.
Reply
#19
HTTP.sys is faster than Indy although not noticeable in most cases.

I suspect something else was going on, likely unrelated to http.sys.
Reply
#20
(05-26-2021, 04:31 AM)pgnair Wrote:
(05-25-2021, 01:41 AM)pgnair Wrote:
(05-23-2021, 06:28 PM)kudzu Wrote: HTTP.sys and SA have different procedures to enable SSL.

https://blog.boxofbolts.com/ssl/windows/...d-windows/

Thank you. It is working now. Awaiting responds from the client

Client reported slowness issue on SYS mode so rollbacked to the Indy mode.

This is unexpected.

Did you test the performance yourself in your test environment?  What's the spec of the server?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)