You are viewing limited content. For full access, please sign in.

Question

Question

Repository Access Advantages Over Server Objects

SDK
asked on January 12, 2016

I'm looking for more information comparing Repository Access (RA) features to those of Server Objects (LFSO). This post and this post give the impression that the advantages of RA over LFSO are only these:

  • Compiled as .NET assemblies
  • Somewhat more intuitive
  • Has a few newer convenient methods

 

Does RA offer any advantage over LFSO from a performance standpoint?

Does RA have any other advantages over LFSO?

What advantages are anticipated that RA will have over LFSO in the future?

Does RA (and Document Services) still have any shortcomings compared to LFSO (and DocumentProcessor)?

 

0 0

Replies

replied on January 13, 2016

Hi cliff, 

It's true that the documentation examples are still a bit sparse for RA, BUT we have a number of example sample projects installed as part of the SDK package. I'd encourage you to check them out if you haven't had a chance.

I would support the premise of doing new integrations in RA. I expect it will be a while before we phase out LFSO compatibility (simply due to backwards compatibility purposes), but more and more new features are being optimized for RA, and more and more of our own products are using RA. 

1 0
replied on January 21, 2016

Justin, we will plan to default to RA for future development projects. In prioritizing the conversion of old projects to RA from LFSO, we were hoping for any performance metrics, features, or LFSO EOL information to support a business case for upgrading.

1 0
replied on January 13, 2016

Bryon - Per the posts you reference my suggestion would be to go with RA for any new project as a general rule.  RA is the newer technology and at some point I assume Laserfiche will phase LFSO out.  Per my earlier post the only drawback that I have experienced with RA is a general lack of documentation and example code snippets for RA.  Much of the SDK help files for RA just enumerate the object properties and methods without any additional supporting text.  (You could get much the same information by just browsing the classes in the VS object browser!)

My assumption is that as each successive version of the SDK is published the RA documentation will continue to become more robust.  In the meantime there are several developers that routinely respond to code questions on this forum, they are an excellent resource if you need additional help.

You are welcome to contact me via email at cprimmer@qfiche.com as well...

0 0
replied on January 21, 2016

Cliff, thank you very much for your response and offer for assistance in the future. I appreciate you sharing your experience.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.