开云体育

I use ARUser to connect to a cluster, makes it easy to set filters and such.
I then start either Writelog during a contest or Spot Collector during non
contest times, and set them to connect to my local copy of ARUser.

Is there a way to have Spot Collector NOT disconnect my ARUser session when
it closes? Just have it disconnect from the local aruser, instead of
sending the bye, which then disconnects ARUser from the cluster?

Thanks

Charlie
KI5XP

Even if SpotCollector didn't send the "Bye" or terminate the TCP/IP
connection, Windows would automatically close the TCP/IP connection
when SpotCollector terminates. A shared TCP/IP connection would
require developing a third application that manages the connection
on behalf of its two clients, SpotCollector and ARUser.

Out of curiousity, when you're running SpotCollector, why are you
running ARUser?

73,

Dave, AA6YQ

--- In dxlab@..., "Charles Morrison" <cfmorris@...>
wrote:

I use ARUser to connect to a cluster, makes it easy to set filters

and such.

I then start either Writelog during a contest or Spot Collector

during non

contest times, and set them to connect to my local copy of ARUser.

Is there a way to have Spot Collector NOT disconnect my ARUser

session when

it closes? Just have it disconnect from the local aruser, instead

of

sending the bye, which then disconnects ARUser from the cluster?

Thanks

Charlie
KI5XP



[Non-text portions of this message have been removed]

I dont see how its a shared tcp/ip connection though. ARUser connects to
the cluster on port 23 (or special port if necessary) and then Spot
collector connects to loopback on port 7300. The connection to ARUser from
Writelog's packet telnet will sever the connection with ARUsers telnet
daemon, but wont kill ARUsers session to the cluster. Data received by
ARUser from the cluster is forwarded to whatever application is currently
connected to it.

The reason I use ARUser is because its extremely easy to set the filters, it
gives me an idea of the status of the cluster (nodes and users), a simple
interface for reading messages, and a convenient way to do announcements and
chats with other users. Also, if Im playing in a contest, I dont have any
of the DXLab apps open, i'll have only Writelog or WL/MMTTY. So instead of
having 2 users connected to the cluster I connect to the loopback daemon on
ARUser.

Its only recently that I started the forray into SpotCollector. So instead
of using a variety of connections to different clusters, I just configured
SC to connect to the loopback. I guess the rest is just habit. Its a nice
program, it also offers some things that I havent found or didnt look for in
any of the DXLab apps yet. Old habits are hard to break! :)

Charlie
KI5XP



_____

From: dxlab@... [mailto:dxlab@...] On Behalf Of Dave
Bernstein
Sent: Friday, April 07, 2006 9:55 AM
To: dxlab@...
Subject: [dxlab] Re: Spot collector question


Even if SpotCollector didn't send the "Bye" or terminate the TCP/IP
connection, Windows would automatically close the TCP/IP connection
when SpotCollector terminates. A shared TCP/IP connection would
require developing a third application that manages the connection
on behalf of its two clients, SpotCollector and ARUser.

Out of curiousity, when you're running SpotCollector, why are you
running ARUser?

73,

Dave, AA6YQ

--- In dxlab@..., "Charles Morrison" <cfmorris@...>
wrote:

I use ARUser to connect to a cluster, makes it easy to set filters

and such.

I then start either Writelog during a contest or Spot Collector

during non

contest times, and set them to connect to my local copy of ARUser.

Is there a way to have Spot Collector NOT disconnect my ARUser

session when

it closes? Just have it disconnect from the local aruser, instead

of

sending the bye, which then disconnects ARUser from the cluster?

Thanks

Charlie
KI5XP

_____

YAHOO! GROUPS LINKS



* Visit your group "dxlab <> " on
the web.


* To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...
<mailto:dxlab-unsubscribe@...?subject=Unsubscribe>


* Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<> .


_____

AA6YQ

--- In dxlab@..., "Charles Morrison" <cfmorris@...>
wrote:

I dont see how its a shared tcp/ip connection though.
ARUser connects to the cluster on port 23 (or special port if
necessary) and then Spotcollector connects to loopback on port
7300. The connection to ARUser from Writelog's packet telnet will
sever the connection with ARUsers telnet daemon, but wont kill
ARUsers session to the cluster. Data received by ARUser from the
cluster is forwarded to whatever application is currently connected
to it.

I didn't think it was a shared connection either until I read the

above paragraph. ARUser is in fact providing a shared connection to
the Cluster -- sharing access between itself and whatever is
connected to port 7300.

The reason I use ARUser is because its extremely easy to set the
filters, it gives me an idea of the status of the cluster (nodes and
users), a simple interface for reading messages, and a convenient
way to do announcements and chats with other users. Also, if Im
playing in a contest, I dont have any of the DXLab apps open, i'll
have only Writelog or WL/MMTTY. So instead of having 2 users
connected to the cluster I connect to the loopback daemon on
ARUser.

Its only recently that I started the forray into SpotCollector. So
instead of using a variety of connections to different clusters, I
just configured SC to connect to the loopback. I guess the rest is
just habit. Its a nice program, it also offers some things that I
havent found or didnt look for in
any of the DXLab apps yet. Old habits are hard to break! :)

SpotCollector's primary capabilities are

- combines multiple spots of the same DX station in the same mode on
the same band into a single spot database entry

- highlights spot database entries of stations whose confirmation
you need by referencing your DXKeeper log

- can filter spot database entries by callsign, DXCC entity, band,
mode, needed, transceiver frequency, continent, origin, or
combinations thereof (full SQL is available)

- double-clicking on a spot database entry QSYs your transceiver to
the appropriate band and mode, taking into account the appropriate
offset for digital modes and the appropriate QSX for split frequency
pileups

- plots spots on DXView's world map

- captures and displays propagation parameters (solar flux, A-index,
K-index) over the past solar revolution, and provides them to DXView
(for its auroral oval display) and PropView (for forecast generation)

- captures and combines DX and WWV spots from up to 4 telnet
clusters, the DX Summit web cluster, and a local packet cluster

- shows real-time distribution of newly-created spot database
entries by band and location

While one normally monitors SpotCollector's Spot Database

Display, one can display a window showing the connection to any
connected cluster in order to view or send announcements or messages.

73,

Dave, AA6YQ

Have you seen ARUser? If ARUser would work within the abilities of
DXLabLauncher, I would use it instead of SpotCollector. It's gorgeous,
it's incredibly simple to use, it's easy to read, easy to control
filters, easy to "recapture" info - the list goes on.

I haven't figured out exactly how to use it with DXLabs so I've
currently stopped using it.

Art - K4IRS

I spent 15 minutes Googling for ARUser yesterday, but could come up
with nothing beside a couple of references in Usenet postings.

Can you provide a URL?

73,

Dave, AA6YQ

--- In dxlab@..., "Art Burke" <aburkefl@...> wrote:

Have you seen ARUser? If ARUser would work within the abilities of
DXLabLauncher, I would use it instead of SpotCollector. It's

gorgeous,

it's incredibly simple to use, it's easy to read, easy to control
filters, easy to "recapture" info - the list goes on.

I haven't figured out exactly how to use it with DXLabs so I've
currently stopped using it.

Art - K4IRS

--- In dxlab@..., "Dave Bernstein" <aa6yq@> wrote:

Even if SpotCollector didn't send the "Bye" or terminate the

TCP/IP

connection, Windows would automatically close the TCP/IP

connection

when SpotCollector terminates. A shared TCP/IP connection would
require developing a third application that manages the

connection

on behalf of its two clients, SpotCollector and ARUser.

Out of curiousity, when you're running SpotCollector, why are

you

running ARUser?

73,

Dave, AA6YQ

73's Rick N2AMG
Aim:n2amg
Yahoo:n2amg

Thanks, Rick.

I didn't correlate "ARUser" with VE7CC's cluster interface -- which
I have seen before.

73,

Dave, AA6YQ

--- In dxlab@..., Rick Ellison <rellison@...> wrote:

73's Rick N2AMG
Aim:n2amg
Yahoo:n2amg

I spent 15 minutes Googling for ARUser yesterday, but could come

up

with nothing beside a couple of references in Usenet postings.

Can you provide a URL?

73,

Dave, AA6YQ

--- In dxlab@..., "Art Burke" <aburkefl@> wrote:

Have you seen ARUser? If ARUser would work within the abilities
of DXLabLauncher, I would use it instead of SpotCollector. It's

gorgeous,

it's incredibly simple to use, it's easy to read, easy to

control

filters, easy to "recapture" info - the list goes on.

I haven't figured out exactly how to use it with DXLabs so I've
currently stopped using it.

Art - K4IRS

--- In dxlab@..., "Dave Bernstein" <aa6yq@> wrote:

Even if SpotCollector didn't send the "Bye" or terminate the

TCP/IP

connection, Windows would automatically close the TCP/IP

connection

when SpotCollector terminates. A shared TCP/IP connection would
require developing a third application that manages the

connection

on behalf of its two clients, SpotCollector and ARUser.

Out of curiousity, when you're running SpotCollector, why are

you

running ARUser?

73,

Dave, AA6YQ

Yahoo! Groups Links

ARUser has all the "stuff" at www.ve7cc.net

Art - K4IRS

--- In dxlab@..., "Dave Bernstein" <aa6yq@...> wrote:

I spent 15 minutes Googling for ARUser yesterday, but could come

up

with nothing beside a couple of references in Usenet postings.

Can you provide a URL?

73,

Dave, AA6YQ

--- In dxlab@..., "Art Burke" <aburkefl@> wrote:

Have you seen ARUser? If ARUser would work within the abilities

of

DXLabLauncher, I would use it instead of SpotCollector. It's

gorgeous,

it's incredibly simple to use, it's easy to read, easy to

control

filters, easy to "recapture" info - the list goes on.

I haven't figured out exactly how to use it with DXLabs so I've
currently stopped using it.

Art - K4IRS

--- In dxlab@..., "Dave Bernstein" <aa6yq@> wrote:

Even if SpotCollector didn't send the "Bye" or terminate the

TCP/IP

connection, Windows would automatically close the TCP/IP

connection

when SpotCollector terminates. A shared TCP/IP connection

would

require developing a third application that manages the

connection

on behalf of its two clients, SpotCollector and ARUser.

Out of curiousity, when you're running SpotCollector, why are

you

running ARUser?

73,

Dave, AA6YQ