This is the class in question. http://docs.wxwidgets.org/stable/wx_wxddeserver.html#wxddeserver
And I stand corrected, this would fix the port problem ONLY on Windows. On Unix, we need to switch to code that avoids their emulated dde and uses file system sockets. Adam On 8 April 2013 14:12, Adam Kennedy <adamkennedybac...@gmail.com> wrote: > The port is used for the single instance server. > > Padre will connect to that port, and expects the server to respond > immediately with a line that says that the server on that Port is a Padre > instance. > > If it doesn't, then Padre starts up (I assume in since instance mode). > > A better approach than this would be for someone to overhaul the > single-instance support anyway. > > The ideal solution is that WxWindows itself supports the necesary API for > doing single instance support "properly" on each platform, but nobody would > add that API to the Perl Wx bindings. > > If we have better control over the evolution of Wx than when I was working > on Padre actively, by far the best solution is to have it added to Wx.pm > and then port to using that instead of my hand-rolled approach. > > > > On 8 April 2013 10:52, Paul CLaessen <p...@claessen.com> wrote: > >> As for Padre using port 4444 .. >> >> As I just found out, there already IS a simple way to change the port >> number: >> >> Just select Tools -> Preferences -> Advanced >> .. and change the setting for: >> >> main_singleinstance_port Host Positive Integer 4444 >> >> into something not used by something else. >> >> (As for bringing this on to myself: I would say, no: openOCD brought this >> on: IT uses 4444, not me!) >> >> (Also: IF something can be changed about this port usage, then maybe it >> should be the fact that Padre simply doesn't start when this port is in >> use >> by something else, without giving any clue as to why it doesn't start: a >> warning somehow somewhere would be nice!) >> >> Kind regards, >> >> ~ Paul Claessen >> >> >> > -----Original Message----- >> > From: padre-dev-boun...@perlide.org [mailto:padre-dev- >> > boun...@perlide.org] On Behalf Of kevin dawson >> > Sent: Monday, April 08, 2013 12:47 PM >> > To: padre-dev@perlide.org >> > Subject: Re: [Padre-dev] TCP port 4444 >> > >> > On 2013-04-08 17:34, Sebastian Willing wrote: >> > > Hi Paul & Kevin, >> > > >> > > we should add support for a customized port, maybe using a config >> > > option or an environment variable. >> > > >> > > Paul: I suggest, that you change your Padre/Constant.pm in the >> meantime. >> > > It's very far from being perfect, but will be a quick fix (until the >> > > next update). >> > > >> > > Kevin: Pointing out that a port is reserved, isn't very helpful for a >> > > development system. >> > >> > iana is a kind of gentlemen's agreement, by convention you honour the >> the >> > registered ports, neither of us are registered. >> > >> > >> > as for what, how and why, and do we still need to use a port, perhaps >> would >> > you like to enlighten us all. >> > >> > regards >> > kevin >> > >> > > I'm running up to three or four different webservers on different >> > > ports on a busy development day plus some databases, Memcache, >> > > Gearman, etc. A dev system commonly uses custom ports and a >> > > "standalone" software like Padre shouldn't block (other) development >> > > components which might not be as easy movable like Padre is. >> > > >> > > Regards, >> > > Sebastian >> > > >> > > On 08.04.2013 18:19, kevin dawson wrote: >> > >> On 2013-04-08 17:01, Paul CLaessen wrote: >> > >>> I noticed Padre is listening on TCP port 4444. >> > >>> >> > >>> Is there a way to either disable this, or change it to a different >> > >>> port number? >> > >>> >> > >>> (It conflicts with my openOCD server) >> > >>> >> > >>> And just out of curiosity, what is it used for? >> > >>> >> > >>> Kind regards, >> > >>> >> > >>> ~ Paul Claessen >> > >>> >> > >>> >> > >>> >> > >>> _______________________________________________ >> > >>> Padre-dev mailing list >> > >>> Padre-dev@perlide.org >> > >>> http://mail.perlide.org/mailman/listinfo/padre-dev >> > >> Paul, you are correct >> > >> >> > >> 1, what is it used for, >> > >> >> > >> set in Padre::Constant >> > >> >> > >> >> > ########################################################## >> > ########### >> > >> # Config Defaults Needed At Startup >> > >> >> > >> # Unlike on Linux, on Windows there's not really # any major reason >> > >> we should avoid the single-instance # server by default. >> > >> # However during tests or in the debugger we need to make # sure we >> > >> don't accidentally connect to a running # system-installed Padre >> > >> while running the test suite. >> > >> # NOTE: The only reason this is here is that it is needed both during >> > >> # main configuration, and also during Padre::Startup. >> > >> use constant DEFAULT_SINGLEINSTANCE => ( WIN32 and not( >> > >> $ENV{HARNESS_ACTIVE} or $^P ) ) ? 1 : 0; >> > >> >> > >> # It would be better if we had fully dynamic collision awareness >> > >> support, # so that Padre could automatically port hop. >> > >> # In the mean time, just make sure that dev, test, and production >> > >> versions # of Padre use different ports, so they don't collide with >> each >> > other. >> > >> use constant DEFAULT_SINGLEINSTANCE_PORT => ( >> > >> $ENV{PADRE_DEV} ? 4446 >> > >> : $ENV{HARNESS_ACTIVE} ? 4445 >> > >> : 4444 >> > >> ); >> > >> >> > >> 2, I think the conflict is all of your own doing see info below >> > >> >> > >> # Updated from http://www.iana.org/assignments/port-numbers and >> > other >> > >> # sources like >> http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/services . >> > >> # New ports will be added on request if they have been officially >> > >> assigned # by IANA and used in the real-world or are needed by a >> debian >> > package. >> > >> # If you need a huge list of used numbers please install the nmap >> > package. >> > >> >> > >> have a look at -> >> > >> http://www.iana.org/assignments/service-names-port-numbers/service- >> > na >> > >> mes-port-numbers.xml >> > >> >> > >> regards >> > >> kevin >> > >> >> > >> >> > >> >> > >> _______________________________________________ >> > >> Padre-dev mailing list >> > >> Padre-dev@perlide.org >> > >> http://mail.perlide.org/mailman/listinfo/padre-dev >> > >> >> > > _______________________________________________ >> > > Padre-dev mailing list >> > > Padre-dev@perlide.org >> > > http://mail.perlide.org/mailman/listinfo/padre-dev >> > > >> > >> > _______________________________________________ >> > Padre-dev mailing list >> > Padre-dev@perlide.org >> > http://mail.perlide.org/mailman/listinfo/padre-dev >> >> _______________________________________________ >> Padre-dev mailing list >> Padre-dev@perlide.org >> http://mail.perlide.org/mailman/listinfo/padre-dev >> > >
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
