308 reputation
38
bio website
location
age
visits member for 3 years, 3 months
seen Oct 19 at 13:47

Oct
12
comment avoiding multiple calls to SQL while being modular
I've really not been able to profile the application because we are still in the design phase. I just feel that making three trips to a server when one trip can do the job is taking too many liberties too early. I could be wrong on this thought and Im willing to listen to critcism on this point.
Oct
12
comment avoiding multiple calls to SQL while being modular
the application which I described above is not yet written. At this point in time the possibility of individual views being required is not yet 100% But they are being written just because eventually they will be required as per the requirements we know today, which could also change in the future. what exactly did you mean by writing down a non-functional requirement ?
Oct
12
comment avoiding multiple calls to SQL while being modular
Thanks MSW for the comment. But could you expand a bit on why it would be reduntant? Each of those are doing different things.
Oct
12
asked avoiding multiple calls to SQL while being modular
May
30
comment Securing web services
both look the same to me, but I guess any clarity helps. I've committed your edits. Thanks.
May
30
comment Securing web services
Thanks. I was actually going for security at a conceptual level. assuming of course, all the basic things are done, like putting in https. In WCF you can actually send a user name password in the header or you can send the token. Keeping https in both ways, what would be the justifications of using one over the other? there must be some situation where one way favors the other and vice versa...
May
30
comment Securing web services
@BartvanIngenSchenau: in 'vs' situation you are looking at a clear winner. I'm not trying to find one winner here, but trying to understand which one is best suited under what particular condition. Its those conditions that I want to talk about; perhaps someone can talk of a third way as well?... The last para should have made that clear. If it isn't let me know.
May
30
asked Securing web services
Jan
29
awarded  Peer Pressure
Jan
20
accepted How to manage and estimate unstructured requirements received from customers
Jan
20
accepted Software Architecture - From design to sucessful implementation
Oct
25
revised How to manage and estimate unstructured requirements received from customers
added 619 characters in body
Oct
25
comment How to manage and estimate unstructured requirements received from customers
Yes, I do that in all cases where we don't budget in a BA.
Oct
25
asked How to manage and estimate unstructured requirements received from customers
Sep
21
comment Software Architecture - From design to sucessful implementation
-ve markers please leave a comment so I can frame my questions better next time:) I've seen many other questions here that don't "fit" the format but have got some good responses to it.
Sep
21
comment Software Architecture - From design to sucessful implementation
+1 for the point about being ignored :)
Sep
20
revised Software Architecture - From design to sucessful implementation
cleared out an ambigiuos point in the question
Sep
20
comment Software Architecture - From design to sucessful implementation
sorry about that. what I meant was, where appropriate. Obviously you wont be able to apply OOP in ETL. My bad, will correct it. Thanks for pointing it out :)
Sep
20
asked Software Architecture - From design to sucessful implementation
Jul
8
awarded  Yearling