Elmar,

Great news. Here¹s what to do. Create a bugzilla bug, attach the code code
to it and then email Jeesmon (the HSS owner) (cc-ing higgins-dev at all
times!) and tell him that its there. Make sure that the code follows the
source guidelines here [1] and [2], etc.

--Paul

[1] http://wiki.eclipse.org/Developer_Team_Page#Source_Code
[2] http://wiki.eclipse.org/Developer_Team_Page#Documentation


On 7/30/09 4:20 AM, "Elmar Eperiesi-Beck" <[email protected]> wrote:

> We are proud to announce, that we completed the integration of our Windows
> Mobile Cardspace Solution into Higgins as Connector.
>  
> SoŠ Šwhat to do now with the code? ;-)
> Mary, are you able to start the IP Process inside the eclipse-community. As
> far as we know, we got rid of all external libs and do only have source code
> written on our self.
>  
> I´m looking forward on working closer together
> Elmar
>  
> ----------------------------------------------- Existing Communication
> ------------------------------------------------------------
> Hi Elmar,
> 
> See ## inline. Thanks for your response. We look forward to working with you.
> 
> On 7/14/09 4:51 AM, "Elmar Eperiesi-Beck" <[email protected]> wrote:
> Paul, Jeesmon,
> thank you for your help. We got all the technical information and hat a chance
> to review them.
> 
> The Connector API seems to be a very lightweight implementation, so it would
> make sense for us to implement a CardSpace connector for the Integration of
> our mobile Cardspace Selector.
> 
> ## Great.
> 
> If the future of Higgins HSS will be HSS and Connector in the same process, we
> will develop the connector in that way. Can we use the ConnectorClientApi.h
> anyway or is there another API to use?
> 
> ## Jeesmon is working on checking in some the new stuff (with HSS + Connectors
> in the same process), so I think you need to wait for that. Jeesmon can answer
> you better than I.
> 
> After this we would be happy to support Higgins by sharing our ³yet closed
> source code² on how to connect a HBX via dll-connection to the HSS with
> Higgins.
> 
> ## This is very interesting as it will solve the problem that you mentioned of
> some locked-down enterprises not allowing installation of apps with open
> sockets/ports, etc.
> 
> ## But I have a question. One of the great things about the current design is
> that HSS is basically just a pipe that routes ANY message from some plugin
> (e.g. HBX) through to the user¹s choice of selector. There is no API, etc. it
> doesn¹t look at the message packages it just gets them from A to B. So.... The
> benefit of this is that there¹s never a need to change, or update HSS as new
> kinds of messages are sent through the pipe. [We are working on other plugins
> that send different messages to the selector than just the usual CardSpace
> ³getToken² message.] My question is do you think you could design a DLL
> solution that would also (somehow) work as a ³dumb² pipe?
>  
> Our plan is to start developing the solution end of this week ­ therefore it
> should be no problem to get it done until Oct ­ Higgins 1.1 ;-)
> 
> How can we share our code ­ should we commit it into a special branche on the
> Higgins project? Then we need an account and some login parameters.
> 
> ## Okay, I need to explain something. The Eclipse process (that Higgins uses)
> is very strict. Before new ³committers² can get write access to the SVN they
> have to create a (small) track record of contributions and then the other
> committers have to vote them in. We¹ve gone through this process many times
> and it is very easy. The first step is to move conversations like this one
> (e.g. this email) onto the higgins-dev list. Then, after about 60 days I can
> make the argument (by pointing to public evidence in bugzilla and higgins-dev)
> that <some> Corisecio developer has been contributing code, patches, ideas,
> emails, etc to other existing committers (like Jeesmon) to commit. We have a
> vote, the developer is voted in and now Corisecio has a Higgins committer.
> 
> ## In the meantime ANYBODY can create an account to post to higgins-dev and
> anybody can use this account to log in to bugzilla. So that¹s the way to
> start. See [1]
> 
> ## I have a request. Would it be possible to have one of your developers join
> the weekly higgins-dev call (just this once). The meeting is at noon eastern
> time zone (16:00 UTC) on Thursday. We could discuss the HSS thing in person
> for 5-10 min on the phone with the whole group.
> 
> [1] http://www.eclipse.org/higgins/getting_started.php
> 
> Regards
> Elmar
>  
>  
>  
> 
> Von: Paul Trevithick [mailto:[email protected]]
> Gesendet: Dienstag, 7. Juli 2009 20:53
> An: Elmar Eperiesi-Beck
> Cc: Brian Walker; Jeesmon Jacob; Mary Ruddy; Bruno Quint
> Betreff: Corisecio and the Higgins Selector Switch
> 
> Elmar,
> 
> I hope you received the technical information from Jeesmon about the Higgins
> Selector Switch (see [1] and [2]) that is being developed as part of Higgins
> 1.1. We are happy to continue supporting you (and along the way improving the
> Higgins wiki doc) for this component.
> 
> We continue to be interested in pursuing the idea of having Coresecio join us
> in working on this component within the Higgins project. It seems to me that
> this would give Coresecio a strategic advantage. As we discussed, you could
> add the hooks into HSS for a Coresecio connector that would in turn connect
> over IP or bluetooth to a mobile phone. We ultimately want to drive (e.g.
> through the ICF [5] and OASIS) the concept of a selector switch into Windows
> (and other OSes) so having a good open source reference implementation of the
> interfaces is important to getting adoption. And we¹d like something like the
> HBX to be built into browsers.
> 
> We plan on releasing Higgins 1.1 in Oct (although it may slip), and having a
> solid HSS (and HBX) is very important. You have pointed out to use (and I have
> noted here [3]) that there is likely a problem with the architecture of HSS on
> Windows. Assuming this is true, then we¹d welcome your help in adapting HSS to
> be more enterprise-Windows-user compatible. And we¹d like to get it fixed
> BEFORE Higgins 1.1 is released.
> 
> Your thoughts?
> 
> Cheers,
> --Paul
> 
> [1] http://wiki.eclipse.org/Higgins_Selector_Switch
> <http://wiki.eclipse.org/Higgins_Selector_Switch>
> [2] http://wiki.eclipse.org/Components_1.1#Higgins_Selector_Switch_.28HSS.29
> <http://wiki.eclipse.org/Components_1.1#Higgins_Selector_Switch_.28HSS.29>
> [3] http://wiki.eclipse.org/Higgins_1.1_Plan#Higgins_Selector_Switch_Component
> <http://wiki.eclipse.org/Higgins_1.1_Plan#Higgins_Selector_Switch_Component>
> [5] http://informationcard.net <http://informationcard.net>
> 
> 
> 
>  
> 

_______________________________________________
higgins-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/higgins-dev

Reply via email to