Prevent Conversion of same Drawing file to svf File again when Forge Viewer is called
up vote
0
down vote
favorite
We have integrated AutoDesk Forge Viewer. We are sending a request to the Forge API's for conversion (using Model derivative API). After closing the Viewer, If we need to show the same file again, Currently we are posting the dwg file again for conversion to view it.
Instead is there a way so save the svf file in my local system so that I need not call the Forge web service twice for the same file.
According to the pricing, for every simple conversion job, its going to cost 0.2 credits.
Please suggest how I can avoid this same conversion second and n number of times.
Thank you,
Shiva Kumar
autodesk-forge autodesk autodesk-model-derivative
New contributor
add a comment |
up vote
0
down vote
favorite
We have integrated AutoDesk Forge Viewer. We are sending a request to the Forge API's for conversion (using Model derivative API). After closing the Viewer, If we need to show the same file again, Currently we are posting the dwg file again for conversion to view it.
Instead is there a way so save the svf file in my local system so that I need not call the Forge web service twice for the same file.
According to the pricing, for every simple conversion job, its going to cost 0.2 credits.
Please suggest how I can avoid this same conversion second and n number of times.
Thank you,
Shiva Kumar
autodesk-forge autodesk autodesk-model-derivative
New contributor
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have integrated AutoDesk Forge Viewer. We are sending a request to the Forge API's for conversion (using Model derivative API). After closing the Viewer, If we need to show the same file again, Currently we are posting the dwg file again for conversion to view it.
Instead is there a way so save the svf file in my local system so that I need not call the Forge web service twice for the same file.
According to the pricing, for every simple conversion job, its going to cost 0.2 credits.
Please suggest how I can avoid this same conversion second and n number of times.
Thank you,
Shiva Kumar
autodesk-forge autodesk autodesk-model-derivative
New contributor
We have integrated AutoDesk Forge Viewer. We are sending a request to the Forge API's for conversion (using Model derivative API). After closing the Viewer, If we need to show the same file again, Currently we are posting the dwg file again for conversion to view it.
Instead is there a way so save the svf file in my local system so that I need not call the Forge web service twice for the same file.
According to the pricing, for every simple conversion job, its going to cost 0.2 credits.
Please suggest how I can avoid this same conversion second and n number of times.
Thank you,
Shiva Kumar
autodesk-forge autodesk autodesk-model-derivative
autodesk-forge autodesk autodesk-model-derivative
New contributor
New contributor
New contributor
asked 2 days ago
Shiva kumar
12
12
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Unless the DWG file has changed, you do not need to upload the DWG file again and/or POST a translation again. If you do this, you will effectively consume 0.2cc. Instead, just reference the URN you had received after upload/translation when starting the viewer. The 'bubble' or SVF persists on the backend depending of the storage policy you chose. For example, if you create a transient bucket, the file and bubble will persists for 24h, temporary for 1 month, and persistent forever.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Unless the DWG file has changed, you do not need to upload the DWG file again and/or POST a translation again. If you do this, you will effectively consume 0.2cc. Instead, just reference the URN you had received after upload/translation when starting the viewer. The 'bubble' or SVF persists on the backend depending of the storage policy you chose. For example, if you create a transient bucket, the file and bubble will persists for 24h, temporary for 1 month, and persistent forever.
add a comment |
up vote
0
down vote
Unless the DWG file has changed, you do not need to upload the DWG file again and/or POST a translation again. If you do this, you will effectively consume 0.2cc. Instead, just reference the URN you had received after upload/translation when starting the viewer. The 'bubble' or SVF persists on the backend depending of the storage policy you chose. For example, if you create a transient bucket, the file and bubble will persists for 24h, temporary for 1 month, and persistent forever.
add a comment |
up vote
0
down vote
up vote
0
down vote
Unless the DWG file has changed, you do not need to upload the DWG file again and/or POST a translation again. If you do this, you will effectively consume 0.2cc. Instead, just reference the URN you had received after upload/translation when starting the viewer. The 'bubble' or SVF persists on the backend depending of the storage policy you chose. For example, if you create a transient bucket, the file and bubble will persists for 24h, temporary for 1 month, and persistent forever.
Unless the DWG file has changed, you do not need to upload the DWG file again and/or POST a translation again. If you do this, you will effectively consume 0.2cc. Instead, just reference the URN you had received after upload/translation when starting the viewer. The 'bubble' or SVF persists on the backend depending of the storage policy you chose. For example, if you create a transient bucket, the file and bubble will persists for 24h, temporary for 1 month, and persistent forever.
answered 2 days ago
cyrille
1,3461416
1,3461416
add a comment |
add a comment |
Shiva kumar is a new contributor. Be nice, and check out our Code of Conduct.
Shiva kumar is a new contributor. Be nice, and check out our Code of Conduct.
Shiva kumar is a new contributor. Be nice, and check out our Code of Conduct.
Shiva kumar is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239258%2fprevent-conversion-of-same-drawing-file-to-svf-file-again-when-forge-viewer-is-c%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password