awesome! is there a maximum filesize for this? I can imagine that 20mb+ oar
files may cause problems? I would like to implement an oar template
loader/saver into a webinterface. This would really make things easier. Any
suggestions how to make save-oar work in a centralized infrastructure?
My test was with an 18Mb OAR file - took a little while to stream in as
it downloaded, but the server seemed happy enough to wait for it to
arrive, and restored all the contents successfully. Your mileage may
vary, but this is fantastic stuff - with OARs on the web and mergeable
OARs, that's a lot
I recently had the same idea - I started implementing the new MonitorModule in
core, it should be pretty easy to extend with new instrumentation. The only
gotcha is I have every instrument return a 'double' value so we can easily
chart it externally (and make easy comparisons).
Adam
here are some large examples you guys can experiment with:
http://nebadon2025.com/oars
Enjoy.
On Sat, Nov 28, 2009 at 6:04 AM, Jeroen van Veen j.veen...@gmail.comwrote:
awesome! is there a maximum filesize for this? I can imagine that 20mb+ oar
files may cause problems? I would like to
whoa. sorry for spamming the list with my modern art poetry. fwiw... i was
replying via my g1 (android phone.) apparently there are still some kinks to
work out of it's mail client.
so anyway, fwiw, i _have_ been working with node.js on Ubuntu. it's mostly
the bomb. i'm unashamed to admit my love