On Tue, Aug 21, 2012 at 4:32 AM, Vincent Torri <[email protected]>wrote:
> Hey > > another mail for the status on Windows: > > 1) cserve2 is not even compiling as shm_open() and (worse) fork() are > used in a part of the code that should be OS independent. If cserve2 > is going to be e required dep for the next evas, i fear that the > Windows development will stop. You were supported to do a port of cserve2 to Windows or other Non-Linux platforms: - _cserve2_slave_proc_run() could be changed to be specific of that platform. It uses fork(), exec() and pipe(), but you can replace the whole function with something that makes sense on windows. Just cope with read_cb() and dead_cb() and you're fine! - you need a different main loop file, see evas_cserve2_main_loop_linux.c, Very likely we can move the slave manager code into a _linux.c as well? - slave and server communicates heavy data using shmem. That's the most efficient system on linux, you'll need to figure out what's the best to use on Windows. It must be HIGH PERFORMANCE. If you can keep a similar API, then good we add a wrapper, otherwise we'll have to abstract that in cserve2, slaves and evas library itself. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
