kimbomadsen

Hi,

My guess is that Indy do not detect disconnection until the time when you try to send something due to it being a blocking non async transport, while the native transports are pure async transports, and any changes from the stack will be signalled back as soon as possible.

/Kim

Hi,

I am looking into the leak.

/Kim

It will fix the state data leak too yes.

/Kim

I will in the fix release also provide a new global kbmMWShutdown method, which will be used for signalling all long running parts of kbmMW to shut down as soon as possible.

/Kim

When using messaging for request/response, it is in reality not the transport that is blocking since that is by definition non blocking, and in the native transports even more so (since the none blocking appearance is simulated using Indy which internally really _is_ blocking…. confused?? 🙂 )

But what is really blocking it is the…[Read more]

Hi,

The ASettings argument is simplified YAML format. It use a property: value scheme where the property name and value follows the YAML syntax for strings.

YAML strings only needs to be quoted if there can be a misunderstanding of the strings composition.
Check this link for more…[Read more]

Hi,

I suppose you are talking about Indy Client messaging transport vs native Client messaging transport?

/Kim

Hi,

Problem is that I do not see a server unresponsive situation. In fact the server continues fine, but no screens are forwarded in my case and I can switch on the fly to GDI.

I’m running on dual Titan V cards.

So it will probably need some debugging on your specific setup to figure out where it hangs.

/Kim

Hi,

Fixed in fix release.

/Kim

Hi,

I do not see server freezing in my setup, but I do see it no longer grabbing screenshots.
In my case it is because the DirectX stuff is running out of resources of some reason (code 0x80070057).

One reason could  be that my screen is 5120×2500.

Switching back to GDI makes it capture fine again without problems.

If indeed your server…[Read more]

Hi,

Will fix in fix release.

/Kim

Damn!

Well.. it will be in the bugfix update to be released shortly.

/Kim

Hi,

I have changed it for 5.20.

/Kim

Grr…. it is a problem due to the use of TBitmap in threads.

It has always been somewhat scary to use TBitmap in a multithreaded environment. But it usually worked, when one remembered to lock the canvas before use.

However I think something has changed in the locking mechanism, since TBitmap.Canvas.Lock quite often ends up in a deadlock…[Read more]

Hi,

Yes it will automatically attempt a lookup of the property text in the phrase section.

Sp it would look for sCancel in phrases.

/Kim

Hi,

You also need to enable the “masterswitch”:

i18n.LearnProperties := True;
i18n.Load(”, ‘test.yaml’,true);

/Kim

Thx
Is in upcoming release.
/Kim

Check new release about to be released to see if it solves the problem for you.
/Kim