NetTalk Training day 2 is a go for launch!
The p_web.ProcessLink procedure's embed is a very common place to put code. For instance you might use this to set an owner attribute (threaded, of course) so that in a multi-company site the server opens the right database for the user.
glo:owner = p_web.GetSessionValue('ownerstring') !You've already stored the ownerstring value in the session at login
NetTalk supports logging to the Windows system log, which you can view with Microsoft's (formerly SysInternal's) DbgView utility.
There are template options to add various debug statements to the log.
The log will also show the thread in use - in one of Bruce's demonstrations he typed into a locator quickly and one thread executing a request for filtered data started before the previous request had finished. This makes for high performance since everything is asynchronous and there's no waiting for another request to complete.
This is a good way to get to know how NetTalk works.
Anything string from a p_web method is always clipped.
Lots of good information about filtering, use of keys, PROP:SQL, locators. NetTalk has some really cool locators, including the ability to search more than one column at a time.
Bruce talked at some length about browses. We tend to think of browses more as procedures, but especially for the web it's important to see the browse as a control, and to consider all of the different ways you can style browses. They're just repeating data.
More to come...