On 01/04/2012 02:00 PM, Corey Ashford wrote:
> On 01/04/2012 01:41 PM, Jeff Johnston wrote:
>> On 01/04/2012 02:55 PM, Corey Ashford wrote:
>>> On 01/04/2012 11:46 AM, Jeff Johnston wrote:
On 01/04/2012 02:10 PM, Corey Ashford wrote:
> Hi Jeff,
>
> I ran across an interesting probl
On 01/04/2012 01:41 PM, Jeff Johnston wrote:
> On 01/04/2012 02:55 PM, Corey Ashford wrote:
>> On 01/04/2012 11:46 AM, Jeff Johnston wrote:
>>> On 01/04/2012 02:10 PM, Corey Ashford wrote:
Hi Jeff,
I ran across an interesting problem with using the URI's that are
formed
in
On 01/04/2012 02:55 PM, Corey Ashford wrote:
On 01/04/2012 11:46 AM, Jeff Johnston wrote:
On 01/04/2012 02:10 PM, Corey Ashford wrote:
Hi Jeff,
I ran across an interesting problem with using the URI's that are formed
in the linuxtools plug-in. I wonder if you have any thoughts on this...
We
On 01/04/2012 11:46 AM, Jeff Johnston wrote:
> On 01/04/2012 02:10 PM, Corey Ashford wrote:
>> Hi Jeff,
>>
>> I ran across an interesting problem with using the URI's that are formed
>> in the linuxtools plug-in. I wonder if you have any thoughts on this...
>>
>> We end up with URI's that look som
On 01/04/2012 02:10 PM, Corey Ashford wrote:
Hi Jeff,
I ran across an interesting problem with using the URI's that are formed
in the linuxtools plug-in. I wonder if you have any thoughts on this...
We end up with URI's that look something like:
remotetools:///
The problem that I ran into is
Hi Jeff,
I ran across an interesting problem with using the URI's that are formed
in the linuxtools plug-in. I wonder if you have any thoughts on this...
We end up with URI's that look something like:
remotetools:///
The problem that I ran into is that if I instantiate a URI object based
on on
