On Mon, Mar 15, 2010 at 3:47 PM, Mindaugas Kavaliauskas <dbto...@dbtopas.lt> wrote:
> Unfortunately, HTTP is stateless and session key stored in cookie is the key > to solve a problem (still not very comfortable...). > > Here I see the main difference between web application and GUI remote > application. Thanks for your comment. I'm trying to follow the J2EE blueprints to "repaint" the apps around public objects like Application, Session, Page and Request but keeping the GT code working. It seems to me that using a single public object ( that has a single hash to hold all the data ) for Application and Session greatly helps to control the data that can be easily cleaned, saved/restored, inspected. So a function can be inside a dynamically loaded HRB or in a DLL and still easily access oApplication, oSession. best regards, Lorenzo _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
