Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
TeamSite
TeamSite, LiveSite and OpenDeploy
Direct publishing to web pages
Migrateduser
Excuse the lack of info on my part and the (likely) ignorance of MediaBin terms...
I've been working on a project to upload existing images in a SQL database to MediaBin, modify custom metadata, and retrieve the assets to a file share which will be the root of a web subdomain. I've built a loader app which which makes calls to the MediaBin web service, and then stores a generated URL in a database for other apps to consume. I'm trying to determine if this is the right approach, or of we're using the MediaBin product in it's most efficient way, or if we could call it directly from our web pages.
We've been generating a GUID filename, dropping images from our database out to a landing zone with the generated filename, then calling the InsertAsset_UNC to upload them to the correct container. After modifying the metadata for the newly inserted asset via a call to ReviseAssetMetadata, we call the RetrieveAsJPEG_UNC method, specifying the target share name, size etc.
This seems to be very wasteful of resources, needing to have the asset in both the MediaBin database, and in the website file share - our client applications are retrieving the image URL from the (non MediaBin) database, then specifying the URL as the src property of img elements on our web pages.
When we were buying in to the product, we were under the impression that the MediaBin service would provide an asset directly to our web pages at the required resolution etc - from a quick look round the web, it seems it is possible to integrate the product with different CMS packages, but from what I can see, the images need to be pulled from MediaBin as part of the laying out of those pages. We have many applications where we need an image displayed on dynamically generated pages - our initial belief was that the service would provide this at the time the client apps page is served, however our current implementation is dependent on the image being deployed previously to the web root folder. Have we got the implementation completely wrong - is the product capable of real-time serving of images, which would remove the need for our website file share??
Thanks
John
Find more posts tagged with
Comments
There are no comments yet