From: stephan b. <st...@s1...> - 2004-12-21 14:54:30
|
On Tuesday 21 December 2004 15:05, Christian Prochnow wrote: > > i assume it's the same problem as the IOManager example not being > > able to find http handler. > > Ahh ok, now i got you. The 'Process' class only supports spawning > local processes and reading/writing to their stdin/stdout. I would > like to leave this unchanged. Process is a low-level system > abstraction class, which should be as small as possible. > Instead i would implement a IOPlugin "process://" which could do the > job. That way you could do every IO with the IOManager. i agree - this should be based on the IOMgr layer, not Process itself. > > In eshell, before an input command is passed off to a client eshell > > does var and alias expansion on it, plus expansions provided by > > wordexp (man 3). > > Great! I would love it. All i need is write access to the tree... :) BTW: i'm currently working off of the CVS copy from SF. Is that the one you're refactoring, or is that somewhere else? Last night, once i finally realized there was a DLL/symbol problem, i got the IOMgr working (again) on my box. With that i'll be able to implement a single class which can dispatch load/save over http/ftp/file URLs (though the file:// handler always fails with something like "cannot resolve service name"). That is, any handler supported by IOManager will inherently be available as a serialization channel for P::s11n. Pretty cool, i think. :) Speaking of DLL symbols: you can do DLL/plugin registration and loading without reading a single symbol from a DLL. See http://s11n.net/papers/#classloading_cpp The approach described there introduces compile-time, cast-free, 100% type safety for types loaded from DLLs (on the surface that sounds impossible, but it is actually a natural side-effect of templates). -- ----- st...@s1... http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts |