3 ms·

And you're planning on tightly control access to those files in a large organization... how? You're going to write custom apps to do diffs against every file o

by tw04 9y ago

And you're planning on tightly control access to those files in a large organization... how? You're going to write custom apps to do diffs against every file overwrite on upload? And oh, btw, now you've potentially got 200 different copies of the file on various people's laptops. There's a reason why SMB is popular - file sharing among large groups of people who need to modify the files with a web server is a complete nightmare.

wruza 9y ago
People can work on file garbages, I seen that too many times to say otherwise. But once their company starts being non-trash, these actions form into strict processes, responsibilities and access rights anyway. 200 different copies of a file is a red flag of management.
ethbro 9y ago
IMHO, from dealing with it on large corporate client networks, I've never seen SMB solve the problems you mentioned. Either you have an access problem (which you could solve with authentication + authorization in parent's web-based implementation) or you have a modification problem (which is really a revision control problem that I believe SMB doesn't solve at any version?). Which then leads people to tossing everything into Sharepoint (insert tirade here). Which leads to Microsoft not caring about evolving the SMB spec because it would only cannibalize sales. So in essence: SMB cases: "Documents need to be distributed, but not modified by more than one person/team" Revision cases: "Documents need to be distributed, modified by more than one person/team, and redistributed"
- Spooky23 9y ago
  The folks running the place need a clue. I've seen things like what the parent describes in prosecution with tens of thousands of people work just fine. The leakage to sharepoint has nothing to do with SMB, but with the lack of an easy to use search solution. Email and Sharepoint give you search and avoid the need for hierarchical filing systems. Search is often less effective, but the clerical people who would maintain those other systems are long gone.

by tw04 9y ago

wruza 9y ago

People can work on file garbages, I seen that too many times to say otherwise. But once their company starts being non-trash, these actions form into strict processes, responsibilities and access rights anyway. 200 different copies of a file is a red flag of management.

ethbro 9y ago

IMHO, from dealing with it on large corporate client networks, I've never seen SMB solve the problems you mentioned. Either you have an access problem (which you could solve with authentication + authorization in parent's web-based implementation) or you have a modification problem (which is really a revision control problem that I believe SMB doesn't solve at any version?). Which then leads people to tossing everything into Sharepoint (insert tirade here). Which leads to Microsoft not caring about evolving the SMB spec because it would only cannibalize sales. So in essence: SMB cases: "Documents need to be distributed, but not modified by more than one person/team" Revision cases: "Documents need to be distributed, modified by more than one person/team, and redistributed"

Spooky23 9y ago
The folks running the place need a clue. I've seen things like what the parent describes in prosecution with tens of thousands of people work just fine. The leakage to sharepoint has nothing to do with SMB, but with the lack of an easy to use search solution. Email and Sharepoint give you search and avoid the need for hierarchical filing systems. Search is often less effective, but the clerical people who would maintain those other systems are long gone.