MediaBin based application

We are planning to build a small ASP application based on MediaBin using the script model API. This applictation would be a virtual directory on the same level as MediaBin and will have customized version of a simple upload, search and report screens. Bulk of the code will be mostly based on the existing ASPs. Any thoughts/best practices/cautions on this is highly appreciated.

Env: MB 4.5.3/Win 2003

TIA

Find more posts tagged with

Comments

Migrateduser

I just wanted to alert you to the fact that a new MediaBin client platform is scheduled to be built on the existing WorkSiteMP platform. The last scheduled release of MediaBin on the existing platform is scheduled for this Spring. There may be a maintenance release after that, but the plan is to create a .NET MediaBin web client that relies on the Interwoven WorkSiteMP server and the WorkSiteMP client APIs. The WorkSiteMP API is very different from the existing MediaBin COM API. A new MediaBin WEB services API will be created for the new platform that is compatible with the existing WEB services API. Therefore, management is encouraging new development for MediaBin to use the WEB services API.
It is more efficient to use the COM API to build a custom ASP site. We have at least one customer that has created their own web client with a look and feel very different from the existing MediaBin web client. Just be aware that you may need to do some significant work to port your ASP site to the new WorkSiteMP API if you choose to use the existing MediaBin COM API.
Also, not sure if this may affect your work, but we are enhancing the existing WEB client for the Spring release, to include applet based uploads and downloads. This enhancement is primarily to accomodate file sizes large than two gigabytes, but will be optionally available to any installation that so chooses to enable the feature.