Regarding the CurrentQueryId

This is for XML serialization in the DevForce EF Entities and it is used in most cases to serialize the object to XML and then apply an XSLT to it to produce a document.  For example, we have an agreement object that actually has several subclasses that represent different types of agreements that we need to store.  When a user gets the option to click-sign the agreement, we serialize the object to XML and then do an XSLT transform to produce the text for the agreement (the agreement object might have properties on it that are used by the XSLT to product the resulting document).  Therefore the offline cache or invokeservermethod stuff really isn't going to work for us.  Also, usually the XML serialization in these cases is one way, ie representing the object as XML but not necessarily creating the object from XML.  We could obviously implement the IXmlSerializable interface, but would prefer a much more automated XML serialization.