Okay, good to know. So, I guess what I heard were just rumors.
"It (Alfresco Explorer) is currently being phased out in favor of Alfresco Share."
The statement "because Explorer is no longer supported" is not true.
Yes - no new features are planned to be added to Explorer.
Hmmm. Well, that's too bad. Share is at least one generation in basic functionality behind Explorer, and it also does not scale as well as Explorer does.
I'm not sure what you mean with the scalability comment - Share can be deployed on (one or more) separate Tomcat servers and distributes more processing to the client's browser rather than the Repository. Did you have a particular use case in mind?
The book is right, but Alfresco Explorer won't go away for a long time yet.It is getting no further development, just bug fixes.We are not sure yet how many development cycles it will take to completelyreplace Explorer with Share, probably another 2 product release cycles, so3.4 and then 3.5. At that point everything should be set to deprecatedExplorer.
At that point everything should be set to deprecatedExplorer.
Well someone probably needs to be more careful about what they are saying.Up to the last sentence agrees with what has already been said on this thread.But At that point everything should be set to deprecatedExplorer. In my opinion there's no way Explorer will be deprecated or "unsupported" in two releases' time. In order to deprecate Explorer, first Share would need to reach feature parity with Explorer and then all the paying customers need to migrate to Share. I don't imagine either of these happening any time soon.
Retrieving data ...