[mapguide-internals] Raster provider problems...

[Traian Stanev]

Yes I understand all that. 
 
But mostly working is way better than none at all. That's all I was trying to say.
 
That, or every request for a raster -- even for formats that would work fine -- will have to pass through the same critical section in order to synchronize access. I wouldn't call that an enterprise class solution either.
 
 
Traian

	-----Original Message----- 
	From: mapguide-internals-bounces at lists.osgeo.org on behalf of Frank Warmerdam (External) 
	Sent: Sat 4/7/2007 12:40 PM 
	To: MapGuide Internals Mail List 
	Cc: 
	Subject: Re: [mapguide-internals] Raster provider problems...
	
	

	Traian Stanev wrote:
	> I think it's worth it to just change the capability to per-connection-threaded and see what happens.
	> Seems like we need experimental verification.
	
	Traian,
	
	I'm not sure what you mean by experimental verification.  Are you hoping
	to verify that it works in per-connection-threading?  Of course, it mostly
	will.  But "mostly" is a pretty weak position to take for enterprise class
	software.
	
	You really can't experimentally prove that software is threadsafe.  At
	mostly you can prove it isn't.
	
	Best regards,
	--
	---------------------------------------+--------------------------------------
	I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
	light and sound - activate the windows | http://pobox.com/~warmerdam
	and watch the world go round - Rush    | President OSGeo, http://osgeo.org <http://osgeo.org/> 
	
	_______________________________________________
	mapguide-internals mailing list
	mapguide-internals at lists.osgeo.org
	http://lists.osgeo.org/mailman/listinfo/mapguide-internals