Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Rovingeye

#1
Anything else we might add? /
March 18, 2004, 12:35:46 PM
When I talked about performance, I didn't mean the time taken in the call, just that I want to have a single machine running a number of servers for different things, smtp, chat ... and using the current net-select means I am wasting cycles polling the sockets rather than the OS handling things.
#2
Anything else we might add? / Lock server
March 18, 2004, 05:57:21 AM
my first network code was to build a simple socket based lock server, after lots of playing with the file locking stuff I found when I hammerd on it hard it didn't lock properly.



My lock server is a simple newlisp process that handles incoming connections, and a very simple protocol of 'l' for give me a lock, and 'u' for release my lock. The server returns a '1' when you are given a lock, and '0' when its unlocked. I even handled connection being droped with a lock would release the lock to another waiting process. I tired a number of alternative, but it always seemd the lock process was consuming too much cpu resources, either by using the timeout in the select, or a simple sleep. If I increased the timeout/sleep too far the process became unresponsive. (anyone wants the code, let me know)



I would like to experiment with p2p, and clustering, but I'm worried about performance with the current net-select system.



Care should be taken with passing experssions across the network, this is the obvious way to go, but is a very big security risk, unless there is a method in place to check their authenticity.
#3
newLISP in the real world / Too Fast :)
February 26, 2004, 08:28:44 AM
Well I tried it, I think its a little too fast, I had to do it again just to make sure it had done it right the first time.



Very cool



Thanks Again.

Darren
#4
newLISP in the real world / Version 7.5.4 is out
February 25, 2004, 09:32:23 PM
I see the new version is out, I have something to look forward to now when I go into work :)



Thanks
#5
newLISP in the real world / Thank you
February 23, 2004, 01:54:19 PM
Thanks a lot for the very quick response, the code for the scale was some stuff I was playing with at work, and I wanted to wait until I had tried it until I replied.



Well I tried it and it works wonderfully. I have even tweaked things a little, so I can pass back a control id into newlisp so I know which slider was played with :)



The XML performance improvments I look forward too, and will let you know how I get on.



I'm still thinking about the sxml tree access/manipulation. Having written my own library, I have gotten used to a way of doing things that doesn't exactly seem to map to newlisp, but then perhaps I should just take my C/C++ head off :)
#6
newLISP in the real world /
February 19, 2004, 07:38:25 PM
I looked back at the newLisp-tk manuals, and followed the example, but I still seem to get the same problem, everything works fine, upto the point I drag the control, then I get the error I supplied. To me it looks like TK is supplying the value of the control as a parameter, but newlist doesn't expect this.



I will try next week to get the ok to send you some files, the latest one I was playing with was around 650k, newlisp seemed to be taking seconds to read this file instead of msec. I was using your solution to convert the file into an SXML and saving that, once converted the files is much faster to load.



I had some other problems about editing XML trees in memory, but I think after re-reading the manual I could write some helpers that should help ease the pain, and keep the performance, I'll let you know how I get on.



I have been playing around with the blog code, with an eye to using it to build a website. although with my experience gained from playing with the XML I am tempted to switch the file format to SXML.
#7
Just like to say I am new to lisp, but seem to have settled with newlisp as a very clean, concise language that is allowing me to get all kinds of work done.



I have one problem, I am new to both lisp, newlisp, and TK, so there is a chance its a silly mistake on my part. On win32 I create a scale control, but when I link it with a -command to newlisp I get:



wrong # args: should be "Newlisp command"

wrong # args: should be "Newlisp command"

    while executing

"Newlisp {(set-value)} 0"

    (command executed by scale)



I assume (and by playing with the slider) I have found the 0 is the current value of the slide.



Thanks

Darren



P.S.

My only other problem is the xml-parser is way to slow :) I cheat, and convert my xml into s-expression for debugging code. But I would be laughed at if anyone here saw how slow the reader was.