It was my understanding that the "NetworkFileSystem" component (https://www.outsystems.com/forge/Component_Details.aspx?ProjectId=99) had all of the same features, but was the better choice because it could do impersonation. Have those features been included in this component? If so, can we get "NetworkFileSystem" to either be deprecated or merged with this so there's no confusion which one is the "right" one?
Thanks!
J.Ja
Hi Justin,
Maybe I could be wrong, please correct me if was the case, but in my point of view, these components are really different.
Filesystems -> Manipulate files on the same machine where your Outsystems Server is installed
NetworkFileSystems -> Manipulates files on different serves using domain, username and password fro network to do it.
Best regards
Fabio
Fábio Fantato wrote:
The NetworkFileSystem component *can* manipulate local files. It accepts a path, which can be a local path like "C:\Windows\Blah\Blah\Blah" or it can be a UNC path like "\\SERVER\ShareName\Blah\Blah\Blah". The only difference (that I know of) is that NetworkFileSystem allows you to provide credentials to access that directory, while FileSystem will just be running as the IIS user and not do any impersonation, which should never get you access to anything.
That is why there is no good reason for there to be two separate components. This should have that functionality added, so NetworkFileSystem can be removed, and users can only find one of these components and not be confused.
First only existed this one. Than someone extended it in NetworkFileSystems. NetworkFileSystems is based on this one. If you have this one installed and install NetworkFileSystems this will be replaced.
Everything that this does NetworkFileSystems also do it since domain is not mandatory
Regards,
Marcelo
Marcelo Ferreira wrote:
Yes, I am aware of the history, and I know what NetworkFileSystem does.
The question is:
1. Why does NetworkFileSystem still exist? Why is that functionality NOT in this component?
2. Can we get that functionality added to this component, and delete NetworkFileSystem?
NetworkFileSystem is NOT being maintained. It is very dead code. But it has functionality that many people needed, and this component (which IS being maintained... and by OutSystems!) does not have.
So users can either not get functionality they need but have a maintained, supported component, or they can use an outdated component that has the missing functionality.
We need that functionality added to this component. That is the point I am getting at.
Justin James wrote:
Perfect Justin. I got the point. In this case I guess unified both them will be better than keep two different components to do almost the same thing.
But this is something that happens a lot in the forge. There are a couple of components that the users stop taking care of the code that they develop and dont even answer messages. The only option to someone that want to change it is to create a another component. In this one the problem is more evident since this one is mantain by Outsystems. I dont have a solution to it but I think something should change how the forge works.
Yeah, there's a lot of work being done behind the scenes on this issue as a widespread problem (as the person who make the original "sortable" component work, it drives me NUTS how many people made other drag/drop components instead of improving that one!). If this was a community-supported component I would just join the team and fix it myself. :) So I am hoping that someone from OutSystems Labs/R&D can see this, and respond or otherwise provide feedback on this one.