2026/07/22
< 2026
|
Wednesday, July 22, 2026 (#203)
|
|
References |
- main work: Ferreteria FileSys stuff in order to support sftp in FTM
I think I'm going to set a naming convention for quasiconstructors wherein if the basic idea is to construct the object using $A but that means it will also need $B to provide missing information, I will not name the function something like "FromAAndB()" (nor even something clearer but more awkward like "From_A_and_B()") but rather just referencing the starter-info, $A -- like "FromA()".
It looks like I have to expand Sunday's narrative a bit:
Starting from a URL (
USpec) string:
- The
Nodequasiconstructor creates aNodeobject, which then can create on demand:
USpecobject (parsesUSpecstring, providesPSpecstring)PSpecobject (parsesPSpecstring, provides filepath calculations)VenTypeobject (class determined byUSpecobject's protocol-type)VenConnobject (class determined byVenType, provisioned fromUSpecobject's connection info)VenNodeobject (class determined byVenType, provisioned fromUSpecobject's filespec)- The
VenNodeobject can then create on demand:
FilobjectFolobject
- Each of these objects except Node and the ?Spec clades is derived from Aspect and (therefore) has a pointer to its Node-object.
- The main change here is to introduce VenConn, which wraps the connection information for the protocol specified by VenType but does not have a filespec.