Ok, I can see that I misjudged your experience level completely :).
In my experience, users do not understand that sessions expire, they
just think the page is broken, and reload to fix it.
If you want to avoid using asp.net sessions, your problem would be to
keep track of concurrent users.
The session ids are generated randomly by MapGuide, so you would need to
store them somewhere to
test if they are expired later. You cannot re-use an id once it has expired.
Perhaps you can get the same end effect, if you install 2 MapGuide
servers (and 2 WebExtensions).
Use one for authenticated users, and one for anonymous users.
In the serverconfig.ini, you can set the
ClientConnections.MaxConnections value to limit the allowed load
for the anonymous installation. It is not the same as concurrent users,
but will limit the amount of server
power that the anonymous users can get.
In my setups there are no problems serving 10 simultaneous users on a
quad core.
I strongly recommend that you use tiles (baselayers) as that is
basically a render
cache, and significantly reduces load on MapGuide. The bandwidth is
close to the
same, but the tiles can also be cached locally.
I'm pretty sure the MgException (and all other classes) are not
implementing [Serializable].
I did not know about the cross-domain exception problems, thank you for
pointing me to it.
There has been no one willing to put time into maintaining the .Net API
beyond what SWiG
generates. Adding extra code in the generated classes would also mean
more work for each release,
and again, no one has been willing to provide this extra effort.
No, I cannot see the attachment.
Regards, Kenneth Skovhede, GEOGRAF A/S
Pietro Ianniello skrev:
My point is not to use session, so I don't want to use ASP.NET
<http://asp.net/> sessions.
If I want to track sessions, your idea can be good, I would probably
implement something similiar fo non Anonymous users... But in this
case insead of pinging to keep session alive, I would just tell users
to save data because of session expiration. It's WEB. Sessions Expire.
Users must know it... well, this just my opinion! ...and pinging can
lead to various security risks.
The problem is with anonymous users, that is for Web Site with maps
served transparently to users by MapGuide.
"On an infinitely fast machine, MapGuide can serve an
infinite number of users."
..ok! I knew it! I must test!!! This was just to request if someone
had made some tests and to share his/her experience....
"You cannot reference a class directly without referencing the dll
(eg MgException).
You can use a more generic try/catch to read the description
without knowing the type:
try
{
//Bad code here
}
catch (Execption ex)
{
//Also catches MgExceptions and the like
Console.Writeline(ex.Message);
}"
What do you menan? I reference "MapGuideDotNetApi.dll". My problem is
with "cross AppDomain calls". Refer to
"http://winterdom.com/2007/01/makeexceptionclassesserializable"; for an
explanation.
"Btw., your attachment did not make it."
What does it means? You was not able to download my attach?
Anyway, thanks for your answer.
Regards pietro ianniello
------------------------------------------------------------------------
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
