Blog Home  Sign In RSS 2.0 Atom 1.0 CDF  

  def Softwaremaker() :
         return "William Tay", "<Challenging Conventions />"

  knownType_Serialize, about = Softwaremaker()
 

 Saturday, March 26, 2005

A great article by ex-MSFTee Stephen R. Walli on OnLamp.com that deals with the Perspectives on the Shared Source Initiative.

A must read for a great insight into Microsoft and its shared source initiatives and perspectives.

Saturday, March 26, 2005 1:22:30 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Friday, March 25, 2005
    Finally, it is available to the public ! Go get it here. The PressPass is here.
    Friday, March 25, 2005 1:05:36 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  • I am invited to present in the MSDN Briefing on 31 March 2005. This quarterly-held event usually generates a fair amount of interest and the theme for this event will be focused on Security - Secure to Survive Conference.

    And since it is focused on security, the most natural thing for me to talk about would be "How to secure your Web Services". Of course, I would be using Web Services Enhancements (WSE) 2.0 for this talk. Since this will be a Level 200+ session, I will hold off asking the audiences to drill down deep into the security headers with me. I will focus more on the principles and concepts and some demos to get audiences interested in securing their Web Services via a message-based approach rather than a transport-based approach such as HTTPS/SSL.

    If time permits, I will spend a little time near the end of the session to do a quick demo on Indigo, focusing on the WSProfileBinding of Indigo and how easy it is to secure their Indigo Services in the future. Indigo is "secure-by-default". This will be the first time Indigo demos will be shown to the public on MSDN Briefing. Do NOT miss it.

    If you are around the area, do drop by and listen in. More details can be found here.

    Thursday, March 24, 2005 10:09:47 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Thursday, March 24, 2005

    While still playing around with the Indigo March-CTP bits and having lots of fun exploring Addresses, Bindings and Contracts (ABC), I was configuring and playing around with the Instancing behavior of an Indigo Service (which I will talk more about later), I created 4 different services of the same interface type and contract, each implementing a different instance behaviour. I am hosting this svc in IIS and therefore, my endpoint address is provided by the host IIS. Therefore, in my config file, I have this:

        <services>
          <service
              serviceType="IndigoBehaviourInstance.PrivateDischargePatientService"
              behaviorConfiguration="SomeDischargePatientBehavior">
            <endpoint address=""
                      bindingSectionName="wsProfileDualHttpBinding"
                      bindingConfiguration="BindingOne"
                      contractType="IndigoBehaviourInstance.IDischargeProcess,IndigoBehaviourInstance" />
          </service>
          <service
              serviceType="IndigoBehaviourInstance.SingletonDischargePatientService"
              behaviorConfiguration="SomeDischargePatientBehavior">
            <endpoint address=""
                      bindingSectionName="wsProfileDualHttpBinding"
                      bindingConfiguration="BindingOne"
                      contractType="IndigoBehaviourInstance.IDischargeProcess,IndigoBehaviourInstance" />
          </service>
          <service
              serviceType="IndigoBehaviourInstance.SharedDischargePatientService"
              behaviorConfiguration="SomeDischargePatientBehavior">
            <endpoint address=""
                      bindingSectionName="wsProfileDualHttpBinding"
                      bindingConfiguration="BindingOne"
                      contractType="IndigoBehaviourInstance.IDischargeProcess,IndigoBehaviourInstance" />
          </service>
          <service
              serviceType="IndigoBehaviourInstance.PerCallDischargePatientService"
              behaviorConfiguration="SomeDischargePatientBehavior">
            <endpoint address=""
                      bindingSectionName="wsProfileDualHttpBinding"
                      bindingConfiguration="BindingOne"
                      contractType="IndigoBehaviourInstance.IDischargeProcess,IndigoBehaviourInstance" />
          </service>     
        </services>

    As we can see from here, all bindings and contract types are the same related to these 4 different endpoint services...and since the endpoint address is provided by the host, the only thing different is the serviceType, bearing in mind that each service is implemented in by its own class. This does make the above configuration less intuitive as it should be. Flexibility should be given to all different serviceTypes to be configured much more intuitively. In this case, if the serviceType attribute is an element, it allows for that flexibility.

        <services>
          <service behaviorConfiguration="SomeDischargePatientBehavior">
            <serviceType type="IndigoBehaviourInstance.PrivateDischargePatientService" />
            <serviceType type="IndigoBehaviourInstance.SingletonDischargePatientService" />
            <serviceType type="IndigoBehaviourInstance.SharedDischargePatientService" />
            <serviceType type="IndigoBehaviourInstance.PerCallDischargePatientService" />  
            <endpoint address=""
                      bindingSectionName="wsProfileDualHttpBinding"
                      bindingConfiguration="BindingOne"
                      contractType="IndigoBehaviourInstance.IDischargeProcess,IndigoBehaviourInstance" />
          </service>
        </services>

    ...or something to that effect...Now if the (multiple) endpoint elements can be done this way, why not the serviceType ?

    Am I missing something here ?

    Wednesday, March 23, 2005 9:00:12 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Sunday, March 20, 2005
    As blogged earlier, I have been crossing more and more into the Indigo realm and ripping the bits apart to see what it is made of. Some of my immediate work assigments will primarily revolve around Indigo-WSE-SOAP and as someone who works in an SI environment, interoperability is something I am very concerned about and I am therefore very particular on what goes out on the wire.
    Sunday, March 20, 2005 3:31:30 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Friday, March 18, 2005
    I had done a very successful presentation on "Demystifying WSDL" to our Singapore Professional DotNet Usergroup a couple of weeks back. It was a deep technical session that touched base on WSDL and Best Practices of Web Services Deployments.
    Friday, March 18, 2005 2:35:04 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  • I know I have not been posting some real technical stuff on my blog for the last few months...and this is the reason why.

    It started off with a Proof-of-Concept I was working on and some thoughts on WS-Security Headers here. Finally, after months of hard work and long review and edit cycles, one of my 'masterpiece' articles has made it to MSDN Web Services Center. From what I understand from MSFT-Singapore, it is the first time a Singapore Flag is flown on MSDN. Gotta like that. Cool...

    Do check it out here and let me know what you think.

    While this architectural setup may come across as 'complicated' and slightly 'unorthodox' in the real world today, I believe we will see more and more setups of this model as we go along with the wide-acceptance of (standards-based) messaging-based systems in the enterprise mainstream. Key-word here is standards-based. Another thing that I believe will happen with Service-Orientation is that this routing/gateway style approach will become the primary extensibility model.

    Indigo will go a long way in making this happen and I am very excited with the impending launch of it this year. Incidentally, the March CTP Bits of Indigo and Avalon is available to MSDN Subscribers and I believe to the general public soon. Keep your eyes out for it.

    What's next ? I will be crossing over to do more Indigo stuff and there are work assignments for me that is revolved around Indigo-WSE-SOAP. I will update here as we (me, Indigo-bits, WSE*-bits) go along.

    Thanks a million to MattP, MarkF and HerveyW for helping me out with this write-up ... and Sorry, Matt for the constant bombardment of emails and queries.

    Friday, March 18, 2005 12:54:11 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Wednesday, March 16, 2005

    ...or is it purple I am seeing...?

    New exciting work assignments come with the dawn of this impending day in the very near horizon. I will update as we go along.

    Tuesday, March 15, 2005 10:31:50 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  • People who know me knows that I generally dislike the the unproductivity of the development of Web Applications. Clients are asking for more and more complex (== intuitive) user interfaces today which is forcing the developers to handle the complexity of the plumbings of the protocols and other legacy (== it works) innards (== javascript) instead of focusing on solving the business problems. ASP.NET goes a long way in simplifying that technology process. However, the baggage of the protocol (synchronous request-response, state, etc) leaves a lot to be desired by the clients (== users) and the developers.

    The developers at Google are using what people are calling 'Ajax.' Jesse James Garrett at Adaptive Path consulting in San Francisco explains it this way via his blog:

    "Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web."

    Basically Ajax is about using Javascript and the XmlHttpRequest object to do processing on the server after the page loads on the client. You can read about the process in this article.

    The possibilities with this are potentially amazing. "The real challenge here is not figuring out how to make the code work but thinking of interesting ways in which it can be utilized."

    Google Suggest and Google Maps did shake the earth for some people at how Web Applications can be viewed and re-invented using oldER technologies. My fear is that clients will start calling and ask for these interfaces when there are still no clear designing tools around. It seems like, in today's world, everyone is not focusing on staring at angle-brackets, choosing to let the toolkits and toolsets do the walking and talking for them.

    With the above said, now unless Visual Studio comes up with a designer for Web Applications close to that or can Eclipse of the J2EE world step up to the plate to be a tough challenger (and credit must be given to them for achieving tremendous strides over the past few years in catching up with the intuitiveness, productivity and the richness of VS.NET),  it will still remain out of reach to most mainstream commercial developers.

    Now until that happens, and not forgetting Flash gaining huge popularity (Check out this amazing Flash Application that does a one-screen registration with no effects of the http synchronous request-response showing through), does this spell the end of Smart Clients ?

    Only time will tell...

    Tuesday, March 15, 2005 9:32:01 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Friday, March 11, 2005
    MSFT Corp has acquired Groove Networks. As I have heard some insights into Microsoft's plans for its Information Worker Group in terms of increasing business productivity for its customers, this seems to be a testimonial for its committment to do so and it is definitely a step in the right direction.
    Thursday, March 10, 2005 10:09:54 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Thursday, March 10, 2005
    Steve Ross-Talbot, co-chair of the Web Services Choreography working group and chair of Web Services Coordination, talks about the differences between Business Process Execution Language (BPEL) and Web Services Choreography Description Language (WS-CDL) here.
    Wednesday, March 09, 2005 10:25:38 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Friday, March 04, 2005

    Pat Helland, a favourite speaker of mine on Service-Orientation and someone whom many regard as the Architect's Architect is joining Werner Vogels in Amazon.

    Is there a brain drain in MSFT Corp ? OR is it just a process of making way for newer ones ?

    Friday, March 04, 2005 1:31:57 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  • Pun intended on the word "Galestorm" in this post title.

    What strikes me most is the fact that if you read between the lines further, you will noticed that Google and Amazon got mentioned in the same breath. Doesnt that sound eerily familiar ?

    Friday, March 04, 2005 2:47:02 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  • Benjamin Mitchell has written a great article on "Why WSE". On the same note, I have a similar one here.
    Thursday, March 03, 2005 10:43:10 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Thursday, March 03, 2005

    If you are in Microsoft TechED 2005 in Orlando, Florida from June 5-10 2005, you will see something happening during the keynote speech --- which should make your jaws drop with the upcoming plans for .NET. I cannot say much at this point except to say that ASPSOFT has got some great gimmicks for this.

    If you are fan of .NET Technologies, I bet you will still be amazed at what the aggregation of technologies such as Web Services, Smart Client, GDI+ and ClickOnce deployment can do.

    Be there.

    Thursday, March 03, 2005 1:09:25 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Tuesday, March 01, 2005
    This couldn't be written any better.
    Tuesday, March 01, 2005 1:13:57 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  • I have seen all kinds of referral spam on my blog BUT this ?

    http TripleW Dot iaea Dot org/ (International Atomic Energy Agency)

    Tuesday, March 01, 2005 3:05:26 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions