Stay connected to vserver with Xojo

[Joseph Morgan]

I tried testing vStudio as you suggested, connecting to Vstudio and then physically disconnecting the server, and I get application not responding. I will submit to mantis.

Using vCursor wouldn't be a problem for me since I only use vTable (it's just easier for me).

So far, regardless of how I do things, if the connection suddenly becomes unavailable, my application becomes unresponsive for about 50 seconds give or take before I can even attempt to reconnect. I think this would frustrate most users in to force quitting (I know thats what I would do)




On Nov 27, 2013, at 2:02 PM, william humphrey <bill at bluewatermaritime.com> wrote:

> Try testing vStudio with a server on your local network and then
> physically disconnect the server and see what happens. It should not
> crash or freeze. If it does please report to Valentina Mantis.
> 
> On Wed, Nov 27, 2013 at 3:59 PM, william humphrey
> <bill at bluewatermaritime.com> wrote:
>> I went through a very similar problem with Livecode and found out that
>> the app crashed on re-connect after timeout because I was using calls
>> for data that used "vCursor" and I was not destructing every single
>> last one of them.  After I tracked them all down the reconnect crashes
>> went away. It seems that the unrestricted vCursor app behaves like
>> another instance of the database being open so when you open the
>> database again after the timeout closing you end up with an odd second
>> database being open too.
>> 
>> I'm not sure if I'm explaining this correctly as I don't completely
>> understand. So even though using vCursor calls is way much faster than
>> vTable calls you have that problem of being sure that you destroy each
>> one right after using it. This wasn't documented in the V4REV
>> documentation at all.
>> 
>> On Wed, Nov 27, 2013 at 3:29 PM, Joseph Morgan <joseph at checkos.com> wrote:
>>> 
>>> 
>>> I found "Idle timeout in minutes".
>>> 
>>> Thank you for that. I will try it.
>>> 
>>> 
>>> What if the network connection is lost, do you know of an elegant way to deal with that without freezing the app?
>>> 
>>> 
>>> Thanks again!
>>> Joseph
>>> 
>>> On Nov 27, 2013, at 1:05 PM, william humphrey <bill at bluewatermaritime.com> wrote:
>>> 
>>>> You need to edit line in server_x64.ini (in the server folder). This
>>>> line shows how long until timeout. I'm a little confused about how it
>>>> works exactly because you will read there that it says "0" is infinite
>>>> time out but actually I've found that it works better to just put a
>>>> big number there.
>>>> 
>>>> On Wed, Nov 27, 2013 at 2:48 PM, Joseph Morgan <joseph at checkos.com> wrote:
>>>>> I want to run my app on several pc's/macs in my shop and always stay connected.
>>>>> 
>>>>> How are you guys staying connected to Vserver in your Xojo/Realbasic apps?
>>>>> 
>>>>> It seems that after some time (maybe hours later) the connection is no longer working and we get a frozen app.
>>>>> 
>>>>> This may be due to a computer falling asleep or even the server falling asleep.
>>>>> 
>>>>> So I figured I could check the Vconnection, but the app is non-responsive.
>>>>> 
>>>>> 
>>>>> Thank you!
>>>>> Joseph
>>>>> _______________________________________________
>>>>> Valentina mailing list
>>>>> Valentina at lists.macserve.net
>>>>> http://lists.macserve.net/mailman/listinfo/valentina
>>>> 
>>>> 
>>>> 
>>>> --
>>>> http://www.bluewatermaritime.com
>>>> _______________________________________________
>>>> Valentina mailing list
>>>> Valentina at lists.macserve.net
>>>> http://lists.macserve.net/mailman/listinfo/valentina
>>> 
>>> _______________________________________________
>>> Valentina mailing list
>>> Valentina at lists.macserve.net
>>> http://lists.macserve.net/mailman/listinfo/valentina
>> 
>> 
>> 
>> --
>> http://www.bluewatermaritime.com
> 
> 
> 
> -- 
> http://www.bluewatermaritime.com
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina