TIP: Click on subject to list as thread! ANSI
echo: points
to: MARTIN FOSTER
from: AUGUST ABOLINS
date: 2020-04-14 21:15:00
subject: oxp: nodelist situation?

** 14.04.20 - 18:30, August Abolins wrote to Martin Foster:

 AA>>> I'll reveal the aptly named August-Solution a lil'bit later.
 MF>> Come on then, the suspense is killing :-))

 AA>You got it wrong. Suspense is *thrilling*. Covid is killing.
 AA>I'll work on a proper reply to "the solution" later today.

HERE, as promised is the "August-Solution" or the workaround/alternative  
that does NOT require mucking about with switching the primary server  
settings.

I have two servers:

 [1] Tommi, fidonet = primary
 [2] Alan,  fsxnet

When I wanted to freq a file from [1], I never encountered an "issue"  
because OXP always uses the primary

When I wanted to freq a file from [2], it would always call [1]

When I wanted to freq a files from anyone else, the freq would always work  
- because those systems were NOT listed as servers.

SO.. the solution:  If I want to freq a file from [2] (and avoid  
reconfiguring the primary server), simply do this:

(are you ready?  here's the answer)

(I promise to stop goofing around and delaying the answer)

After creating the freq to [2], simply allow OXP to do a normal POLL to  
the [2] server via the N A or N S commands.

Maybe a variation of the last sentence above can make its way into the OXP  
Help system?

This strategy would probably apply nomatter how many additional servers  
are added.  Simply allow OXP to POLL the server for which the freq is  
intended.


  ../|ug

--- OpenXP 5.0.43
* Origin: ------------------------------------------------- (2:221/1.58)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.