In my application I have a service layer which is remoted. There are some functions that are "non-query" methods, that is they do not return a domain entity or collection but perform some action on the server. I would like to get back the result of these calls and possibly any error messages. I am thinking of using a serializable "CallResult" object which has two properties: a boolean "Successful" property indicating if the function executed sucessfully and a "Message" string property containing the message from any exceptions that occured while executing the method. The client would only look at the Message property if the Successful property is false.
I am wondering if this is a good design or not and if there are any common alternatives.
One example would be a something like
Public CallResult AuthenticateUser(Credentials credentials);
If the credentials are valid the server returns a CallResult with a Successful property of true and an empty Message property (or possible a string to store the "ticket" or some such). If not successful, Message would contain the reason, such as "Invalid password", etc.
Thanks for any advice.
"CallResult" class for non-query RPC
Hot Topic
- WildCard Error in Application Definition File Error with custom application
- can't create workflow - sharepoint designer 2007
- Persistent Sharepoint Server Error Events
- OHSBE Web Service DB Access Exception
- View Sharepoint data within CRM
- SOA and Banks
- Profile Manager and RDF Vocabulary
- Queries on SPS 2003
- WSS V3 mail alerts
- if not to use session variables then what
SharePoint Products
- How to listen to a web service for a message receive.
- Code Generation - MyGeneration, CodeSmith, GAT/GAX or DSL?
- Message Routing doesn't work
- WSE 3.0 Security
- MOSS2007 Office integration...good, better, best document.
- Creating Visio Diagrams in an ASP.Net Web Form Programmatically (C#)
- Auto create a workspace - event handler or workflow designer?
- How do i get my web part to remember input when it reloads ???
- MOSS2007 Active Directory connectivity configuration
- adding sharepoint website user
"CallResult" class for non-query RPC
PiGuy
cippyboy
I think it is a good option in the context of what you are doing (I would probably go with a different approach altogether and use explicit messages for communicating to/from the services - but that is another story)
Arnon