Subj : Long FileNames :( :(
To   : Benny Pedersen
From : mark lewis
Date : Mon Jul 06 2009 03:23 pm


 BP>> bbbs should have spotted the problem for you before any other
 BP>> noticed it 
 ml> why?

 BP> i belive software that accept errors is basicly bad writed in the
 BP> first place 

this is true but one must also fully understand all the aspects of the 
technologies involved...

 ml> IIRC bbbs does LFNs with no problem...

 BP> janis just tested it for us above :)

incorrect... i'm am very aware of numerous systems that transfer LFN files over 
8.3 connections without any problems... there are several factors involved... 
one being that the mailer receiving the file can handle LFN->8.3 conversion on 
the fly AND that the inbound TIC file accompanying the file also understand the 
name conversion...

 ml> it is the other systems that cannot where the problem arises...

 BP> as always, its not my fault :)

no, i'm saying that (part of) the problem is on the receiving systems...

 ml> it is they who need to do the footwork to adjust the filename for their 
 ml> local filesystem... no only the file processors but the mailers as well 
 ml> ;)

 BP> mailers dont care about lfn or not, but bso does, aso have lfn as
 BP> default 

mailers SHOULD care about their local file system's capabilities and also make 
allowances for other mailers they connect with that cannot handle LFNs...

this discussion was done a long time ago when the major developers of fidonet 
software were still active... some of those capabilities were implemented and 
some were not... then some devs drifted away and others arose and the main 
fidonet development echo, NET_DEV, got broken somehow and folk today still 
don't know about it or try to find it...

)\/(ark 

 
* Origin:  (1:3634/12)

.