V11 Server Question
John Foster (7/1/08 12:52PM)
Peter Jakobsson (7/2/08 11:15AM)
Peter Jakobsson (7/2/08 11:32AM)
John Foster (7/1/08 12:52 PM)
Hi Brad and Brendan,
Having client access to a local 4D data file would be a killer
feature for the future.
Something else that would be nice would be the capability at
startup to try to connect as client, but automatically revert to
standalone if the server isn't available.
I second, third, and... this feature request.
Part of a future project is to design for just an event. If I could
do it all in native 4D (without installing a separate standalone
or?), where I could automate it so the user wouldn't even have to be
aware, this would be perfect.
John...
From: Brad Perkins <bperkins@...
Date: July 1, 2008 9:12:48 AM PDT
Reply-To: 4D iNug Tech <4d_tech@...
Brendan (and others),
Thanks for the quick answers. Having client access to a local 4D
data file would be a killer feature for the future.
Something else that would be nice would be the capability at
startup to try to connect as client, but automatically revert to
standalone if the server isn't available.
Thanks,
Brad
--------------------------------------------------------------
John Foster
Eternity Software
425-486-1622
http://www.eternity-software.com/ES_Products.html
Peter Jakobsson (7/2/08 11:15 AM)
On 1 Jul 2008, at 18:12, Brad Perkins wrote:
Thanks for the quick answers. Having client access to a local 4D
data file would be a killer feature for the future.
Peter Jakobsson (7/2/08 11:32 AM)
Sorry about the double post - my hand slipped on the 'send' button
before I had time to write the reply.
On 1 Jul 2008, at 21:52, John Foster wrote:
Having client access to a local 4D data file would be a killer
feature for the future.
I can see what the problem would be in implementing this feature and
why 4D have never done it so far.
Given that there are 2 'scopes' at the moment - client server &
single user, they would have to introduce a third scope (say 'idle')
in which manages the changeover from Server to Standalone/Other 4D
Server.
However, the 'CHANGE DATABASE' command is going to have to execute in
a method which belongs to one scope or the other - - for example, if
we are in client-server mode it's part of the 4D Server structure, if
we are in 4D-local, it will be part of the local structure.
4D then has to quit, connect to the new database, download a whole
new structure and start executing from On Startup (i.e. not from the
next command after the CHANGE DATABASE command which is perhaps what
some advocates are thinking ?).
For this reason, combined with the fact that we can now access
multiple databases through expicit SQL connections, I can't see them
ever doing it since that '3rd scope' is already there in the form of
the host O/S and said 'killer feature' basically amounts to quiting
and relaunching in a different mode.
One feature that I wouldn't mind having which would not require the
'3rd scope' is the ability to log off 4D server while keeping the
client up. i.e., all your current selections become empty and the
client disconnects from the server programatically. I would like this
so that it frees up resources on the server while client is not doing
anything and we have less ';effective users'. An example of this is a
shop POS system where the client only connects to make a sale but is
able to display the POS screen continuously.
Peter
Reply to this message
Summary created 7/2/08 at 9:21AM by Intellex Corporation
Comments welcome at: feedback@intellexcorp.com