Jump to content

Search the Community

Showing results for tags 'sessions'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • uniGUI Public
    • Announcements
    • General
    • Feature Requests
    • Installation
    • Deployment
    • Other Platforms
  • Licensing
    • Licensing
    • Ordering uniGUI
  • Bug Reports
    • Active Reports
    • Closed Reports
    • Old Bug Reports
  • uniGUI Development
    • General Development
    • uniGUI Releases & Roadmaps
    • Utilities
  • Mobile Platform
    • uniGUI Mobile
    • Mobile Browsers
  • Users Area
    • Sample Projects
    • Components and Code Samples
    • Third Party Components
  • Non-English
    • Non-English
  • Miscellaneous
    • Hosting
    • Server Security
    • Jobs

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. This option would be so useful if it worked. The way it currently works is that, for both srOnePerIP and srOnePerPC, the user can successfully start any number of sessions and, after some delay, all sessions are killed except for the last one. The behaviour is the same regardless type of browser. The fact that the new session terminates a previously loaded busy session is very odd and the fact that it happens without any ability for us to give the user a reason for why the session has been killed is painfully unprofessional. Ideally, when a second session is started this new session it the one that should be immediately terminated and, as part of ServerMessages, we should have a SessionRestrictTemplate option that can be used to display an appropriate error message with some form of elegance. Maybe there is something I don't understand. If so can someone please explain.
  2. How do we interrogate UniServerModule to count how many active live sessions there are ?
  3. I need to make one client send parameters, and others read them. I do not understand how to do this. Here is an example: in browser i sent "demo:1234@192.168.xxx.1:8077/?luxs=46&onoff=0" procedure TMainForm.UniTimer1Timer(Sender: TObject); begin if UniApplication.Parameters.Values['luxs']<>'' then lux1:=strtoint(UniApplication.Parameters.Values['luxs']); UniProgressBar1.Position:= lux1; end; It's work fine for client who sent it. But not for all client sessions. Trying to do an analysis leads to exception: procedure TUniServerModule.UniGUIServerModuleHTTPCommand( ARequestInfo: TIdHTTPRequestInfo; AResponseInfo: TIdHTTPResponseInfo; var Handled: Boolean); begin if ARequestInfo.AuthExists and (ARequestInfo.AuthPassword='1234') and (ARequestInfo.AuthUsername='demo') then begin if ARequestInfo.Params.Values['luxs']<>'' then MainForm.lux1:=strtoint(ARequestInfo.Params.Values['luxs']); Exit; // Authentication is successful end else begin AResponseInfo.AuthRealm := 'Enter credentials for ' + Title; handled:=True; end; end; If you have simple code examples, please write them in this thread/ Thank u!
  4. Hello to all. I am developing an application .exe with the configuration StandaloneServer = True. The application resides on a PC with Win7/64 (but I checked with WinServer2008/64 is the same). In practice, it often happens randomly that when I plug in a new session I get out of the error "Web session terminated". I'm not using the configuration ISAPI / DLL but an exe application. It's need to configure something on IIS or on the PC Server ? Thanks
×
×
  • Create New...