Dougie,

Yes. We started using it when we moved to v15.x. (We had some issues
in v14 and I think I had an engineer tell me something to the effect
of "Right. Use v15." We do get the concessional ghost session which is
mostly a licensing annoyance. We starting the move to v16R6 and doing
a lot of testing. I won't turn on the .dot notation until we have run
snag-free for some time (can't go back to 16.3 once it's turned
on....)

dave

On Fri, Apr 20, 2018 at 1:44 PM, jdcryer--- via 4D_Tech
<[email protected]> wrote:
> Dave,
>
> Whilst I cannot comment on the specific version I will say that everyone 
> should get on board with the new network layer.  Start testing with it and 
> providing as much feedback as fast as possible.  It is the future whether we 
> like it or not.
>
> It has improved through v15, v16 and even v17 but still has many issues 
> related to ghost connections, speed and seemingly random dropouts.  These are 
> incredibly difficult to diagnose and report an clearly there is not enough 
> being done by 4D to debug and resolve (particularly via the internet where 
> there are so many different factors involved.
>
> To make this robust we need to keep the pressure on and provide feedback from 
> the many environments and uses that we have as users and developers.
>
> Regards,  Dougie
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************



-- 
David Nasralla
Clean Air Engineering
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to