[wxPython-users] Distributing a wxpy app - central server or each workstation

[Chris Mellon]

On 3/1/07, Chris Mellon <arkanes at gmail.com> wrote:
> On 3/1/07, Geoff Skerrett <Geoff at teammsa.com> wrote:
> >
> >
> > Thanks for your response we have tried the network share and everything
> > works fine.  We have designed our app to ensure that that the "work" files
> > are unique to the user, so we aren't to worried about those types of
> > collisions.
> >
> >  I guess my questions is more related to .dll's and perhaps it is more about
> > dll's in general than specifically wxpython.  By way of explanation, I am a
> > newbie to development and I have this vague recollection from a conversation
> > several years ago where someone mentioned that .dll's in a Windows
> > environment can't be shared between applications ... might honestly have
> > been from Win95 days and might even have been related to .vbx files, not
> > .dll's at all.
> >
> > So let me apologize my vague question earlier and I will try and be more
> > precise.   I understand that the practice is to install the .dll on the
> > workstation, however, are there any "technical" barriers to have 50
> > instances of the client application using a single set of .dlls loaded on a
> > network share.  -- ie, do .dll's have some sort of locking mechanism that
> > prevents "sharing" or once the app loads the .dll and accesses it's
> > functions/objects is app's instance of the .dll unqiue to that app ?
> >
>
> I suspect that this will end up being more work than it's worth, if it
> works at all. Exactly what are you hoping to gain from doing it this
> way? If you're trying to save bandwidth in deployment, you'll lose it
> from the network traffic every time someone starts the app. The app
> won't work at all, period, if the network goes down. You've still got
> to deploy the app so you don't gain any "no deploy" benefits.
>

To clarify: Running the *whole app* from a single network share will
work and be fine. I read your question as about deploying *only the
dlls* on the network share. When running an executable off a network
share, Windows copies the remote file to the local machine. The remote
files will not be locked and you can upgrade by replacing them and
requesting your users re-start the app.