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

[Rune Devik]

Windows should be able to handle this. It looks for the dll's in both it's
path and in the directory of the application. The only problem I can think
of is if Windows as you say actually locks the dll's when used by one app so
that the second instance is not able to read them. But that makes no sense
since it just reads and not writes.. just fire up more than one instance and
you'll know if this will work or not. I guess your incentive to do this is
to be able to manage the app from just one place so that an upgrade can be
done in one place and not 50. However as previously noted in this thread if
the network goes down this will be a pain..

Regards,
Rune

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 honest=
ly
> 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 ?
>
> G.
>
>  ------------------------------
> *From:* Rune Devik [mailto:rune.devik at gmail.com]
> *Sent:* Thursday, March 01, 2007 10:30 AM
> *To:* wxPython-users at lists.wxwidgets.org
> *Subject:* Re: [wxPython-users] Distributing a wxpy app - central server
> or each workstation
>
> Hi
>
> Well, that should be farly easy to test. Just put your app on one computer
> and share the directory. Mount that as a network share on a different
> machine and fire it up. There could be all kind of problems if your single
> install can't handle multiple clients though. Like all  instanses share t=
he
> same directory to store data and stuff like that.  But I have at least be=
en
> able to run an installer written in wxpython from a network share so ther=
e's
> nothing that stops you from doing this if the app is designed "correctly".
> All the dll's is in the same dir as the app so windows will be able to lo=
ad
> the dll's.
>
> Regards,
> --
> Rune Devik
> http://www.garageinnovation.org
>
> On 3/1/07, Geoff Skerrett <Geoff at teammsa.com> wrote:
> >
> >  This isn't specifically related to wxpython,  but if someone could
> > provide us some guidance it would be appreciated.
> >
> > We are distributing a wxpython application using py2exe.  We have a new
> > client with approx 50 workstation and were wondering if need to install
> > the supporting .dll's on each workstation or could we install these on
> > network share and then have a short cut on workstation desktop that poi=
nts
> > to the .exe on the network share.
> >
> > Thanks for any assistance on this.
> >
> > Geoff.
> >
> >
> >
> >
>
>


-- =

Rune Devik
http://www.garageinnovation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wxwidgets.org/pipermail/wxpython-users/attachments/200703=
01/6ccaa4cf/attachment.htm