Unsolved
This post is more than 5 years old
6 Posts
0
1326
December 20th, 2011 08:00
performance and scalability - object interface vs. namespace interface
Hi,
Atmos programmer’s guid states that the object interface is "
Did anyone check the differences between the two interfaces and have more specific/measured differences?
I intend to archive millions of files (around 4 MB each) and I prefer the namespace interface because the sharableURL option, but I need to know the differences between the two to be able to make the decision...
0 events found
No Events found!
chris_arnett
110 Posts
0
December 20th, 2011 09:00
You can use shareable URLs with the object API, just pass in an ObjectId instead of an ObjectPath (Identifier is abstract).
DarrenSoothill
15 Posts
0
December 20th, 2011 09:00
Why can't you do a shareable URL from the Object interface.
What is the use case and what are the failover requirements from one site to another?
doronm
6 Posts
0
December 20th, 2011 22:00
I know I can use it but in objectId I don't know what's the file name from the URL.
Let's say I'm archiving severakl types of files - (i.e. video and audio files), each has different player software. With objectId the shareable URL return without their original file type / file name. So I cant use the browser to open the file with the correct player...
rbala1
222 Posts
0
December 21st, 2011 06:00
This doesn't address your specific problem, but it's worth mentioning nonetheless because it's related. You can set the content-type when you create the object and Atmos will dutifully send it back when you retrieve it.