Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
Re: How IE handles URL's
From: David Boyle (David.BoyleED.TADPOLE.COM)
Date: Mon Dec 15 2003 - 04:20:59 CST
> -----Original Message-----
> From: Duane Maurer [mailto:duaneramaHOTMAIL.COM]
> Sent: 12 December 2003 03:23
> To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
> Subject: How IE handles URL's
> Russ: Feel free to rewrite this as much as you want...
> IE uses URL Monikers (a COM object used to parse a name of
> another object,
> kinda like a string pointer to another object) to parse out
> URL's by passing
> substrings to a few COM objects for each part, from the file
> urlmon.dll (Url
> Moniker) and that the problem is probably with the BSTR-
> (Unicode string
> with length not expecting NULLs)
Just to clarify - a BSTR is a length-prefixed string of OLECHARs (Unicode
chars) that may contain NULLs.
> Anyway, urlmon.dll should be the only file changed... and
> everyone on this
> list needs to know that IE is very COM based and therefore
> everything is
> broken down into a number of little objects, each of which
> has to be perfect
> to prevent lame bugs like this one... Apparently they are not...
COM-based does not imply "little objects, each of which has to be
perfect..." Indeed, COM is often used in conjunction with the Facade design
pattern which results in a single COM object being used to represent a group
of inter-related C++ objects. As for having to be perfect to prevent lame
bugs - this doesn't make much sense to me. What is it about COM that
Want to reply to the person who sent this message?
This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you''ll have to copy their email address out of the message and place it in your TO: field.