Hello all,
We all know Xojo WebApps don’t do to well at serving up media via sessions. Could a speedy media server be created using webfiles?
https://documentation.xojo.com/index.php/WebFile.Open
[quote=356399:@Daniel Wilson]Hello all,
We all know Xojo WebApps don’t do to well at serving up media via sessions. Could a speedy media server be created using webfiles?
https://documentation.xojo.com/index.php/WebFile.Open[/quote]
Why not let apache or a cdn handle the media files? Each webfile would be in-memory so it could be out of memory soon having multiple sessions.
Hi Derk, thanks for your comment. The Webfile.open method has an InMemory property. If you set this to false the file is only loaded when a request comes in.
Almost all the of the media is dynamic. Apache or a CDN could be used but we are trying to use Xojo so we have better control over the data that is being passed around.
I would like to know:
Is this a viable idea for a high traffic media server? If so, are there any gotchas I should watch for?
Will media be sent as it loads from the disk?
This question has more to do with number of concurrent viewers than Xojo itself.
‘InMemory = True’ means the file is loaded into memory right away so it can be served quickly. If you are serving the same file 500 times it would not be ideal to load from disk every single time. This is the purpose of cache. However you can only cache so much due to memory limitations.
Either way your largest issues are outbound bandwidth, number of concurrent clients, intelligent caching.
Xojo at this point is just reading bits from a file and serving them via HTTP. Any language could achieve that with the same relative ease. In fact some might be more capable at doing it due to better concurrent processing faculties.