HotShoe Well-Known Member Licensed User Longtime User Mar 9, 2014 #1 The MLfiles library is currently a single file containing normal Android file handling and Samba (SMB) file handling. I did this intentionally thinking that a single lib would be easier to use if people needed to do low level file handling across platforms. The drawback is that it requires the jcifs lib be installed to use the library even if you don't need Samba access. So, the question is: Should I separate the library into 2 libs: MLfiles and MLsmb? or leave it as 1 library as it is now? --- Jem
The MLfiles library is currently a single file containing normal Android file handling and Samba (SMB) file handling. I did this intentionally thinking that a single lib would be easier to use if people needed to do low level file handling across platforms. The drawback is that it requires the jcifs lib be installed to use the library even if you don't need Samba access. So, the question is: Should I separate the library into 2 libs: MLfiles and MLsmb? or leave it as 1 library as it is now? --- Jem
JakeBullet70 Well-Known Member Licensed User Longtime User Mar 10, 2014 #2 I use the MLfiles and the Samba part too so I need both. But I would say that the jcifs is large at 387k so separate them. Upvote 0
I use the MLfiles and the Samba part too so I need both. But I would say that the jcifs is large at 387k so separate them.
HotShoe Well-Known Member Licensed User Longtime User Mar 10, 2014 #3 JakeBullet70 said: I use the MLfiles and the Samba part too so I need both. But I would say that the jcifs is large at 387k so separate them. Click to expand... That is my thinking as well. There are a lot of times that I just need the file handling and not the SMB stuff, but I do want some opinions. It's an easy change, but would require checking another library entry in existing projects that use MLsmb. Thanks, --- Jem Upvote 0
JakeBullet70 said: I use the MLfiles and the Samba part too so I need both. But I would say that the jcifs is large at 387k so separate them. Click to expand... That is my thinking as well. There are a lot of times that I just need the file handling and not the SMB stuff, but I do want some opinions. It's an easy change, but would require checking another library entry in existing projects that use MLsmb. Thanks, --- Jem
DonManfred Expert Licensed User Longtime User Mar 10, 2014 #5 dont bump: Do! I dont need SMB so i would prefer two libs instead of one. Upvote 0
