FTP Connection

Yesterday installed pclapcounter 5.33 and started playing with it.
What i discovered is that for every upload of the xml file a new connection is created to the FTP server.
So i presume the process is:
- open connection
- upload file
- close connection

is it possible to leave the connection open and upload the file everytime.
so you don't get so many outgoing connections.
for example:
- open connection
- upload file
- check connection if ok then upload file else open connection and upload file
- repeat previous step.

In this case you don't close the connection everytime but leave it open.

Hey -

I think what happens during a race process is this, from my experience.

New Race - Connection Opened, Grid Status and data updated. Connection closed.
Race Starts - Connection Opened, Racing Status - Connection Remains Open.
During Race - XML File sent in accordance with your frequency.
Race Ends - Last update sent through with XML file, Connection Closes.

Only one connection is active at any given time, so I wouldn't worry about too many instances.

Could you tell me how  you discovered that every upload of the xml file  create a new connection to the FTP server ? , which tools you use ?

In fact the live timing interface use only 1 connection , the connection is opened when the live timing interface start and closed when the live timing interface close:

- Start Live timing interface : connection opened - send xml and html files
- new race - connection remain open - send xml files  
- during race - connection remain open - send xml files every x seconds
- pause race - connection remain open - send xml files every x seconds
- resume race - connection remain open - send xml file every x seconds
- race end - connection remain open - send xml files
- Stop Live timing interface - connection closed

During the race if the connection is lost (the little light in the interface is red) then the live timing interface automaticaly resume the connection.

guy wrote:

Could you tell me who you discovered that every upload of the xml file  create a new connection to the FTP server ? , which tools you use ?

In fact the live timing interface use only 1 connection , the connection is opened when the live timing interface start and closed when the live timing interface close:

- Start Live timing interface : connection opened - send xml and html files
- new race - connection remain open - send xml files  
- during race - connection remain open - send xml files
- race end - connection remain open - send xml files
- Stop Live timing interface - connection closed

During the race if the connection is lost (the little light in the interface is red) then the live timing interface automaticaly resume the connection.

you're right. I don't know what went wrong but now it is how you descriped it.

Bonjour,

Actuellement quand on ferme pclapcounter le fichier .xml est toujours sur le serveur ftp.
Ce qui engendre lors de la réouverture de pclc des informations fausses.

Pour y palier est il possible de proposer via pclc l'effacement du fichier xml afin de rentre le tableau en ligne vide.

J'ai bien dis une option car suivant les cas il faut garder les informations en ligne du résultat final et suivant les cas (lors d'une nouvelle course) il faudrait ner pas avoir le fichier xml afin que pclc le renvoi sur le serveur.

J’espère avoir été claire dans mes propos ?
Sinon je redéveloppe a nouveau, sans soucis.

Merci par avance de ta réponse guy.
G.

Yes the XML file stay on the server until another race overwrite it, i don't think a option is usefull , up to you to delete it yourself

guy wrote:

Yes the XML file stay on the server until another race overwrite it, i don't think a option is usefull , up to you to delete it yourself

Ceci est dommage car nous n'avons pas forcement de client ftp sur l'ordinateur de course.

Il serait très appréciable qu'a la fin de la course ou lors du démarrage et arret de l'interfacele fichier xml soit proposer d'etre effacer.

Ceci permettra de bien voir la mise en grille des voiture a chaque rotation de piste...

De plus,
Lors d'une rotation de piste le fichier xml est bien envoyé (via le refresh) mais pas écraser donc bien que les voitures soient en grille, elles paressent sur le livetiming en pause.
J'ai aussi constater que une fois la pause terminée et le nouveau segment lancé, il faut absolument qu'une voiture passe un tour afin de mettre le tableau live timing a jour, malgré le refresh bizarre, non ?

Merci de ton aide

I test it and i don't have the problem you describe, rrust me the xml file is always overwrited and your problem is not linked to a first cross of SF line.
For me it's linked to a gap into the synchronisation between the XML and the HTML file , when the HTML page read the XML file it could be that the XML file not already content the new data and therefore the leader board of the live timing not show the new data but if you wait the next refresh it will.
For your information the leader board show the date and time of the ranking (the date and time are in XML file in tags "LastUpdateDate" and "LastUpdateTime") so i suggest you to look again and check the date and time of the ranking.

Bonjour,

J'ai debug mon fichier HTML et j'avais omis un "break;" dans le code JavaScript qui a eu pour conséquence de figer le rendu en ligne.

Tout est redevenu OK, merci pour tes réponses hyper réactive.

Re,

Je voulais savoir par quel moyen hardware on peut diffuser en local et en ligne le live timing?
La solution en ligne on la connais tous mais en local ceci est il possible aussi?

Si oui, je veux bien avoir une piste de réflexion niveau hardware et software.

@ bientôt.
Merci

Yes it's possible to have the live timing on your local computer , look here: https://pclapcounter.forumotion.com/t1272-live-timing-on-your-local-computer

guy wrote:

Yes it's possible to have the live timing on your local computer ,  look here: https://pclapcounter.forumotion.com/t1272-live-timing-on-your-local-computer

Merci beaucoup, no comment perfectly.