This has been happening more and more lately with some public clients. Is
there anything that would generically cause this. Why do we have to reboot a
server everyday to make MapGuide work properly? The only solution to this is
a full virtual server reboot. Does the new MapGuide 2.4 solve any
The answer is to go back to the basics. Here is a list of items to check in no
real order.
1) Connection time out interval. If you have viewers on a slow link to the web
server, they may exceed the default timeout intervals. Don't laugh, there are
still people on dial up...
2) Make sure
Great list Martin!
I note there's not much in the way of code mentioned other than to make it
clean.
What is the site using PHP/.Net?
Are you using AJAX or Fusion?
Are you making queries against the database in your code? If so, are you using
native DB connections or FDO. This can be ms vs
Ok I've done a little digging but not sure where to dig really.. so far I can
get my head around the label placement code found in ?
root/trunk/MgDev/Common/Stylization/RS_FontEngine.cpp
If I'm reading through it correctly it should be computing the offset
correctly, I think the extent
Possible related ticket?
http://trac.osgeo.org/mapguide/ticket/772
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/One-more-time-Multiline-tp4944944p4951247.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Yes that sums up my problems pretty good.
So currently it is not possible to justify my text until some code change
has been implemented ?
It sounds like most the work is done and it just needs to be accepted?
--
View this message in context:
