Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
FWIW, on 4D 16.3 32-bit on MacOS 10.11.x server, using the new network layer caused multiple ghosted users every day. Using 4D 16.3 64-bit server, the ghosting pretty much disappears (one particular user still ends up ghosted multiple times), guess I should check their version of 4D. Jim Crate > On Apr 21, 2018, at 11:05 AM, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > From everything I've heard, the new architecture will be a huge step forward > in performance, especially for larger deployments. There's no question that > push is better than poll when you have thousands of processes trying to > communicate (or not) with a server. > > I'm really looking forward to flipping the switch -- I think it's really > close in 16.3 HF2. > > > -- > Jeffrey Kain > jeffrey.k...@gmail.com > >> On Apr 21, 2018, at 7:21 AM, Paul Lovejoy via 4D_Tech <4d_tech@lists.4d.com> >> wrote: >> >> What is spooky is that nobody seems to be 100% behind the ServerNet >> architecture. This means that if we want 64 bit support, we have to go with >> a potentially troublesome network layer. > > ** > 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:4d_tech-unsubscr...@lists.4d.com > ** ** 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
From everything I've heard, the new architecture will be a huge step forward in performance, especially for larger deployments. There's no question that push is better than poll when you have thousands of processes trying to communicate (or not) with a server. I'm really looking forward to flipping the switch -- I think it's really close in 16.3 HF2. -- Jeffrey Kain jeffrey.k...@gmail.com > On Apr 21, 2018, at 7:21 AM, Paul Lovejoy via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > What is spooky is that nobody seems to be 100% behind the ServerNet > architecture. This means that if we want 64 bit support, we have to go with a > potentially troublesome network layer. ** 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
What is spooky is that nobody seems to be 100% behind the ServerNet architecture. This means that if we want 64 bit support, we have to go with a potentially troublesome network layer. Paul > Le 21 avr. 2018 à 01:30, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Hi Jeff, > >> I haven’t tried it yet, but I understand that the old network layer is >> available to all apps in v17. > > You may be on to something, but the documentation still says it doesn't work: > http://doc.4d.com/4Dv17/4D/17/Architecture-of-64-bit-applications.300-3743775.en.html > > Quote: " (*) With 32-bit versions of 4D Server (both platforms) and 64-bit > versions of 4D Server for Windows, you need to make sure that the ServerNet > network layer is activated on the server side, ***since the legacy network > layer is not available in 64-bit versions of 4D***. For more information, > please refer to the New ServerNet Network Layer (compatibility) section." > > I am checking with the team on this. > > -Tim > > > > ** > 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:4d_tech-unsubscr...@lists.4d.com > ** ** 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:4d_tech-unsubscr...@lists.4d.com **
RE: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
Hi Jeff, > I haven’t tried it yet, but I understand that the old network layer is > available to all apps in v17. You may be on to something, but the documentation still says it doesn't work: http://doc.4d.com/4Dv17/4D/17/Architecture-of-64-bit-applications.300-3743775.en.html Quote: " (*) With 32-bit versions of 4D Server (both platforms) and 64-bit versions of 4D Server for Windows, you need to make sure that the ServerNet network layer is activated on the server side, ***since the legacy network layer is not available in 64-bit versions of 4D***. For more information, please refer to the New ServerNet Network Layer (compatibility) section." I am checking with the team on this. -Tim ** 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
I haven’t tried it yet, but I understand that the old network layer is available to all apps in v17. On Apr 20, 2018, at 12:57 PM, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> wrote: >>> Also, in v17 the legacy network layer is available in 64-bit apps if you >>> really need it. > ^ this only applies to 4D Server 64-bit on Windows . ** 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
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 <4d_tech@lists.4d.com> 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:4d_tech-unsubscr...@lists.4d.com > ** -- 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
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:4d_tech-unsubscr...@lists.4d.com **
RE: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
> FWIW, I don't think the 64Bit Mac Servers support the old network layer ^ This is correct. 4D Server 64-bit on Mac requires the New Network Layer. > > Also, in v17 the legacy network layer is available in 64-bit apps if you > > really need it. ^ this only applies to 4D Server 64-bit on Windows . * 4D Server 64-bit on Mac requires the New Network Layer. * 64-bit Clients on both platforms require the New Network Layer. -Tim PENNER ** 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
FWIW, I don't think the 64Bit Mac Servers support the old network layer dave On Fri, Apr 20, 2018 at 3:46 AM, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> wrote: > Paul - All versions continue to support the legacy network layer for 32 bit > applications and Windows 64 bit server. There’s no change here. > > The new network layer seems hugely improved in 16.3 HF2. We run a few > smaller servers (<30 clients) with no problems on this version. We haven’t > tried the 600+ user server yet as it’s such a huge task. > > Also, in v17 the legacy network layer is available in 64-bit apps if you > really need it. > >> On Apr 20, 2018, at 3:37 AM, Paul Lovejoy via 4D_Tech <4d_tech@lists.4d.com> >> wrote: >> >> Hi, >> >> We have been having some intermittent crashes with 4D Server, 150+ users and >> a 120gb database. We use “Execute on server” quite a bit and the release >> notes for 15.5 say a bug was fixed which could cause crashes with Execute on >> server. >> >> We’re preparing to go from v15.4 to v15.5 and it apparently only has the new >> network layer. We have had the legacy layer up until now. >> Is the new network layer ready for showtime now? >> >> >> Does anyone have any experience with that Execute on server bug and whether >> it was resolved with v15.5? > ** > 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:4d_tech-unsubscr...@lists.4d.com > ** -- 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:4d_tech-unsubscr...@lists.4d.com **
Re: Legacy network layer or not: 4D v15 on Mac OS server and v15.5
Paul - All versions continue to support the legacy network layer for 32 bit applications and Windows 64 bit server. There’s no change here. The new network layer seems hugely improved in 16.3 HF2. We run a few smaller servers (<30 clients) with no problems on this version. We haven’t tried the 600+ user server yet as it’s such a huge task. Also, in v17 the legacy network layer is available in 64-bit apps if you really need it. > On Apr 20, 2018, at 3:37 AM, Paul Lovejoy via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi, > > We have been having some intermittent crashes with 4D Server, 150+ users and > a 120gb database. We use “Execute on server” quite a bit and the release > notes for 15.5 say a bug was fixed which could cause crashes with Execute on > server. > > We’re preparing to go from v15.4 to v15.5 and it apparently only has the new > network layer. We have had the legacy layer up until now. > Is the new network layer ready for showtime now? > > > Does anyone have any experience with that Execute on server bug and whether > it was resolved with v15.5? ** 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:4d_tech-unsubscr...@lists.4d.com **
Legacy network layer or not: 4D v15 on Mac OS server and v15.5
Hi, We have been having some intermittent crashes with 4D Server, 150+ users and a 120gb database. We use “Execute on server” quite a bit and the release notes for 15.5 say a bug was fixed which could cause crashes with Execute on server. We’re preparing to go from v15.4 to v15.5 and it apparently only has the new network layer. We have had the legacy layer up until now. Is the new network layer ready for showtime now? Does anyone have any experience with that Execute on server bug and whether it was resolved with v15.5? Cheers, Paul ** 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:4d_tech-unsubscr...@lists.4d.com **
