i was looking owlib for php
we just init and don't init again
i think that any time we make get or put we need to connect, write,
read and disconnect, i'm right?
can we make one connect and after a disconnect? like
while (1){
if (disconnected()){
disconnect();
connect('127.0.0.1:1234');
}
reading...
writing...
}
today i make this way:
init('172.16.0.1:1234');
while (1){
reading...
writing...
}
but i think that connecting and disconnecting is a waste of time, if we
could just connect one time and disconnect when we need could be more
faster to get data or put data
and seeing the --foreground -error-level=9 output i can see that every
read we need a new thread fork
[Thread -1209861200 (LWP 15767) exited]
[Thread -1243436112 (LWP 15762) exited]
[New Thread -1251828816 (LWP 15769)] <==
[New Thread -1218258000 (LWP 15770)] <==
[Thread -1235043408 (LWP 15764) exited]
CALL: owserver: parse path=/uncached/10.6F7EC9000800/temperature
CALL: PARSENAME path=[/uncached/10.6F7EC9000800/temperature]
.....
could we optimize this?
i'm thinking in make an php library for owserver using stream and
sockets, and don't use libphpow.so, or change libphpow.so
what you think?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
