John Bristowe's Weblog

Friday, March 28, 2003

Ingo Joins DM
Make my day!.

Emails like this can really make my day (hyperlinks inserted by me)

Congratulations on passing the test teach with flying colors.
[...]
Welcome aboard Ingo!

Woohoo! [Ingo Rammer's DotNetCentric]

Mucho fantastico. Congrats, Ingo!

2:41:32 PM    comment []

NEWS: Sam Gentile and Friends Win JOLT Award for Groove Toolkit for VS.NET
I/We Just Won a JOLT Award!!!!. I just got word: The VSIP  product that I played a large part in shaping and developing (the first version) , the Groove Toolkit for Visual Studio .NET has just won a JOLT award!!! (scroll down to Langiuages and DEvelopment Enviornments) [Sam Gentile's Blog]

Great stuff! Congrats!

1:20:10 PM    comment []

Targeting Groove Web Services (GWS) with WS-Forums (Interop++)
I felt like experimenting with some preliminary interop between WS-Forums and Groove Web Services (GWS)...

The code unpinning the "Post to Groove Discussion" button utilizes the Groove WSE Output Filter I built a while back to target GWS. Clicking this button posts the discussion entry to the shared space, WS-Forums as an unread item:

FWIW, here's the XML that was generated by the Groove Output Filter to create the new entry in the discussion:

<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<GrooveHeader xmlns="http://webservices.groove.net/Groove/1.0/Core/">
   <TimeToLive>30</TimeToLive>
   <GrooveIdentityURL>grooveIdentity://nsjq2tqkz2rjsfywijznh42bv7bsiteh@</GrooveIdentityURL>
   <GrooveNonce>qs2gkeuw2k4kv5s2s386irc48mhhafn29c88jf2</GrooveNonce>
</GrooveHeader>
</soap:Header>
<soap:Body>
<Create xmlns="http://webservices.groove.net/Groove/1.0/Discussion/">
   <DiscussionEntry>
    <Created>0001-01-01T00:00:00.0000000-06:00</Created>
    <Modified>0001-01-01T00:00:00.0000000-06:00</Modified>
    <Unread>true</Unread>
    <ParentID>-1</ParentID>
    <Subject>Sample Post in unmoderated forum</Subject>
    <Body>Sample post in unmoderated forum</Body>
   </DiscussionEntry>
</Create>
</soap:Body>

</soap:Envelope>

I removed the WS-Timestamp and WS-Routing headers for readability.

I wonder if this proof-of-concept can now target Tim Knip's remote Groove Access Point, which publishes a public discussion to a Web page via his (very cool) grooveInterop Tool for Radio Userland. *SHRUG*

A very possible scenario would be have both sets of SOAP endpoints (that is, WS-Forums and GWS) operate over a fully-duplex "virtual channel"; have WS-Forums invoke the GWS Discussion Web service when a new post (AKA, discussion item) is created and vice versa. In the scenario presented above, the WinForm simply acts as "go-between"; its role is (ultimately) redundant. Ideally, we want this model communicating endpoint-to-endpoint, which shouldn't too difficult to get up & running.

1:39:58 AM    comment []