[Dxspider-support] What to do about web clusters?

[Tim Tuck]

Hi all,

So it seems that a number of web clusters, such as our own, use the 
following valid syntax to post spots on behalf of our users...

'dx by '. $poster. ' ip '. $user_ip. ' '. $entry_freq. ' '. $entry_dx. ' 
'.$entry_message

which results in a spot input looking like this...

03.dat:1741417468^DXCommand^AX2AZ-16 connected from 149.28.170.222 cols 80
03.dat:1741417468^cmd^AX2AZ-16|149.28.170.222|dx|by VK4CZ ip 
1.132.23.174 7074 AO8M  FT8 Tnx QG62LP08<>IM98
03.dat:1741417468^DXCommand^AX2AZ-16 disconnected

Given that the syntax is a valid method for injecting a spot AND web 
cluster users can only do this if they have a username and password on 
the web cluster, and the web cluster pseudo user is also registered on 
the spider node - the spot is valid.


So the network needs to accept spots created in this fashion somehow.

Or... remove that methodology from the software and provide an API for 
web services to post spots.

Or... add support code to the code behind the current syntax to generate 
the appropriate PC statements so that others accept the spots. This 
would mean that all the web clusters do not have to re-write any interface.

Or... turn of the recent "enhancement" and find some other method to 
achieve its intent.


While I accept that the intent of recent changes was to ensure a spot is 
valid by a user on a cluster, none of those users on web clusters really 
are "on" the dxcluster.


Hopefully this can be resolved in some fashion.

regards

Tim

sysop VK2AZ-2


-- 
VK2XAX : QF68KM : ITU59 : CQ30 : ORARC : WIA