World: r3wp

hmm, I would like to know Mike, what actually were you doing? Because 
- in old DBF x-Base days it worked like that - you simply had "cursor" 
at some db position and you moved by using 'skip command .... of 
course even then, it was wise to use indices and to limit the scope 
of data you work with ...

now SQLs are different kind of beasts -  there is NO live connection 
to sql database (on cursors later :-), you simply send a query, SQL 
server prepares results for you and sends it back to you. So, I wonder, 
how could actually SQL server slow your recordset browsing? And IF 
you were sending new requests after a key-press and wanted to stay 
real-time, then it is quite heroic aproach :-) Within our SAP system, 
you are glad if you receive your query result in few secs.

So, mostly, if you work with SQL, you try to find the right context 
of data, limiting your query as much as possible. Then you do a query, 
receive result and browse it. In that case, you already have all 
your data in rebol block already (unless you are reading them from 
port continuously), and it has nothing to do with SQL database anymore 
...

Now on cursors - of course, old x-base aproach is possible with SQL 
too, it is called "live cursor" or something like that. But with 
larger systems, adming don't allow or don't like to see it, as it 
consumes additional resources. Some of databases even don't have 
it. IIRC mySQL will introduce it from version 5.0, or maybe I am 
wrong ....

Not using a cursor. Right key action  increments current-record-key. 
Retrieves single row for current-record-key, Displays page with data 
for row retrieved.  The database is local and only has (so far) 120 
rows but I have another with three hundred shorter records (no BLOBs) 
on it and it works well without any wait.  i.e. I can hold down the 
right key and it will flash each page by.  MySQL protocol has always 
seemed very fast to me.  Is it possible that View is stacking up 
the key actions and hanging after it gets too many?  p.s. I don't 
want to read the whole database content into memory because then 
I have to worry about locking when I allow HTML updates to it by 
others.  Single row updates with the last update 'winning' in the 
unlikely event of a collision works well for what I need to do.

Hello, anyone have any ideas how I might improve on the integrity 
of a program that sends email to a list of people. I just realized 
I should be using '/only' but I have to check its behavior as I don't 
want each person to get a list of the other recipients. My problem 
is I often get a time out and I want to trap that. Yesterday during 
my first test it got halfway through the list and errored out which 
then caused the program to exit. I figured I should at least keep 
a running log so I can go back.

Again, I check but I wonder how the header will behave with an '/only' 
Will the "to:" address be altered?

I guess it has to be a generic address in the header. It doesn't 
change it. Oh, well, that'll work as well.

/only is not good - then ppl will see one each other ...

there is also bcc field available - meaning blind-copy ... in such 
case, you send it with all adresses just once to the server, server 
sends it to each recipient, but they will not see one each other, 
just some "recipient" string or something like that ...

what about putting your send function in an attempt block?

Pekr, it actually didn't do a list. Instead it sent individual emails. 
Also I probed send and there is a '/show'' option that will replace 
the to: address. checking...

how to obey timesouts in general, try following:


either none? attempt [conn: open http://www.rebol.au][print "not 
connected"][print "connected"]

OK, thanks.

alhough I am used to use if not error? try [ .....]

... as 'attempt is functions available from some older core versions 
...

but there were cases , where I failed even inside of 'try block, 
maybe if function contains other functions, dunno ... I am really 
not an expert in all that throwing errors principles ... Ladislav 
or other folks here will do much better service to you :-)

OK, I can't seem to get the show to shove the to: address in but 
I'll keep at it.

then use /header refinement and construct header yourself ...

Well I'm doing each mail individually and it seems to slow that way.

Anyway, setting header/to: none works but it puts the entire list 
there as you mentioned. Hmmm, maybe I have to do it individually.

thanks.

Just wondering how one matches a GUI like VID to an asynchronous 
data source. I am thinking of building a mulit tab panel application 
with an asynchronous backend.  If the user requests some data on 
one screen, and then changes their mind by switching to another screen, 
what does one do with the data when it arrives?  Does one refresh 
the original screen request and move focus from where the user switched 
to ?

Or,  say there is a chat window as part of the application.  How 
does one refresh the chat window without losing the focus on whatever 
the user is currently doing?

maybe some kind of feedback? requester would be to heavy, some blinking 
light "new data"? think of the red in altme-groups

Hmm.

I guess it depends upon whether the updating of the display grabs 
focus or not.

what triggers the data? somebody else like with altme, or more like 
a browser?

well, the data will be sent if there is a chat like aspect to it.

and also if the user requests it.

overlooked your second post. its about relayouting and keeping focus?

maybe I can do it like Altme.

change the colour of the tab for the panel that is updated.

MikeL, I think the problem is as you suspect. Whenever you WAIT for 
something (in your case MySQL), you are also waiting for view events. 
Your view events are arriving faster than the results are in the 
mysql port. Put a simple lock in your code:

 button "next" [if not working? [ working?: yes  next-page  working?: 
 no ]  ; where next-page sends and waits for my-sql port.

James, you can test what happens by sending mail to yourself. If 
you have two accounts then you can test the multiple addresses functionality.

A bit more about my guesses about VID and mySQL. I wasn't sure it 
was not the number of rows that was causing the lockup so I loaded 
100,000 rows into the MySQL table and VID seems to be able to page 
through them based on right arrow (meaning get the next, display 
it, repeat until last row) i.e. hold it down and the row information 
will flash on the screen and eventually catch up.   The hanging seems 
to be a combination of stacked UI events and hitting a mySQL row 
that has a large BLOB in it.   Small text values in the BLOB are 
handled.   I can page past a large BLOB provided that there is not 
an accumulation of UI events.  If there is not a large BLOB in the 
rows being read, then it does not hang when VID is asked to page 
through at a rate it can not quite keep up with.

Mmm. Interesting. Can you identify the precise size of the BLOB needed 
to cause the lockup ?

It is the largest BLOB on this table but is only 13410 bytes.

In request-color a function "setc" is used. I can see it in system/words, 
but I can't see source. I seem to remember a way, or am I wrong?

it's probably in a context with an object. I ran into the same problem 
with request-dir, which someone magically found the context for me, 
for :-)

Found it: system/words/req-funcs/req-color/setc
Thanks for the hint!

how?

I used anamonitor.r found in the library.

probe req-funcs/req-color

Is there still people developing with Rebol/view without using Anamonitor 
??!!

Shame on you

does it work with rebgui ?

I've never used it :-)

It was a time (not so far) where view doc was pretty inexistent.

Anamonitor was (is!) the way to correct partially this "state of 
fact".

Graham: as long as you use View to test Rebgui scripts it should 
works. But with SDK script without View sources include, it must 
not.