aglets-developer — List for Aglets platform developers.

[Aglets-developer] Improper parsing of CGI query string

[Marc M. <ma...@co...>]

The current (1.2) parser in HttpCGIRequestImpl.java does not 
handle "/" characters in a CGI query string.  It considers them token
separators (like the &).  The token delimiter should be removed when
the parsing gets to the query string so the "cgi" variable will be set
to whatever is remaining in the line.

It would also be nice to be able to pass relative path information
to an aglet (e.g. http://aglet:4434/default/aglet/mine/relative/path), 
but that's a bigger change.

Marc

farpoint.tear.com% diff HttpCGIRequestImpl.java HttpCGIRequestImpl.orig
264,265c264
<                       // Marc M - change delimiter to "" to get to EOL
<                       cgi = t.nextToken("");
---
>                       cgi = t.nextToken();

RE: [Aglets-developer] Ticket scheme case sensitive

[Robert B. <rbe...@iS...>]

Marko:

Seems simple enough.  I'll add that to the bug list.  Looks like you have
work around.

// RAB

> -----Original Message-----
> From: Marc Mosko [mailto:ma...@co...]
> Sent: Monday, February 26, 2001 2:55 PM
> To: agl...@li...
> Subject: [Aglets-developer] Ticket scheme case sensitive
> 
> 
> While playing with using HTTP messages to cause aglet 
> dispatch, I found
> that creating a ticket is case sensitive to the protocol name.  The
> error
> is really in java.net.URL.  See below.
> 
> Perhaps in Ticket.java, the function setDestination(...) should have:
> 
> _protocol = destination.getProtocol().toLower();
> 
> Marc

[Aglets-developer] Ticket scheme case sensitive

[Marc M. <ma...@co...>]

While playing with using HTTP messages to cause aglet dispatch, I found
that creating a ticket is case sensitive to the protocol name.  The
error
is really in java.net.URL.  See below.

Perhaps in Ticket.java, the function setDestination(...) should have:

_protocol = destination.getProtocol().toLower();

Marc

----- Sample 1
** Request
farpoint.tear.com% lynx -dump
http://farpoint.tear.com\:4434/aglets/default/ddc/msg_Dispatch\?aglet=edu.ucsc.cse.http.mmosko.Sample\&dest=ATP%3A%2F%2Froaster.tear.com%3A4434

** Tahiti console snips
Mon Feb 26 11:39:33 PST 2001 (BaseUtil): Message <[Message : kind =
msg_Dispatch: arg =
{%querystring%=aglet=edu.ucsc.cse.http.mmosko.Sample&dest=ATP%3A%2F%2Froaster.tear.com%3A4434,
dest=ATP://roaster.tear.com:4434, cgi-response=,
aglet=edu.ucsc.cse.http.mmosko.Sample}: priority = 5]>

java.net.MalformedURLException: unknown protocol: ATP
        at java.net.URL.<init>(URL.java:290)
        at java.net.URL.<init>(URL.java:210)
        at java.net.URL.<init>(URL.java:229)
        at com.ibm.aglet.Ticket.getDestination(Ticket.java:179)
        at com.ibm.aglets.LocalAgletRef.dispatch(LocalAgletRef.java:881)
        at com.ibm.aglets.SystemMessage.handle(SystemMessage.java:200)
        at com.ibm.aglets.AgletThread.run(AgletThread.java:106)


------ Sample 2
farpoint.tear.com% lynx -dump
http://farpoint.tear.com\:4434/aglets/default/ddc/msg_Dispatch\?aglet=edu.ucsc.cse.http.mmosko.Sample\&dest=atp%3A%2F%2Froaster.tear.com%3A4434

(works fine)

[Aglets-developer] Todo List

[Robert B. <rbe...@iS...>]

In an effort to move the 1.2 codebase forward, let's start to compile a todo
list.  :)

Some things that I would like to see worked on:

-- New property that allows you to set the IP address of the server.  Very
useful if DNS does not resolve you machine name to an address.

-- Set-up of the keystore used for security.  Currently, one needs to
manually add keys.

-- Fix login so that userId and password can be removed from the aglet.props
file.

-- Improved server logs possibly using log4j.  Currently logging is
insufficient for public server, IMHO.

-- HTML based context listener thus removing the dependence of ASDK on AWT.

-- Currently, I've been unable to establish a multi-machine security domain.
I'm not sure if this is configuration problem or a limitation of the ASDK,
but I like to see the ASDK be capable of this.

-- Better install facility.

This is just a start.  Thoughts?

// RAB

[Aglets-developer] Aglets1_2 on Solaris 2.7 - Anyone tried it yet ?

[Andrew H. <A.H...@so...>]

All,

Does anyone have any experiences with Aglets (ideally the 1_2 codebase)
running on Sun Solaris release 2.7 ?.

I know that people are playing with various Linux releases, but I haven't
seen anyone posting messages where Solaris is being used. My organisation
is looking at developing an application where Solaris is a prerequisite
hence the question. I assume that the ASDK does not utilise any
non-portable features of Java, but someone may know otherwise.

Any feedback greatly appreciated.

Andy

RE: [Aglets-developer] The Project

[Ferrari, G. D <gre...@lm...>]

I suggest taking a long hard look at the Gnu model for managing open source
with different platforms and versions.  It's tried and true, and seems to be
working very well.

> -----Original Message-----
> From:	Daryl Beattie [SMTP:Da...@sc...]
> Sent:	Wednesday, February 14, 2001 1:37 PM
> To:	'agl...@li...'
> Subject:	RE: [Aglets-developer] The Project
> 
> Duh, okay Gregory please ignore my ignorant postings. :P  That's what I
> get
> for reading my e-mails recent-first! Sorry for making a mess of this nice
> list already -- I'll control my impulses from now on. :(
> 
> I have a question; is it necessary to continue the aglets1_1 code? We can
> always keep it around as the "final IBM release"... but it seems to me
> that
> this should be a CVS branch-tagged version, not a separate code-base. But
> I
> suppose we have what we have, and will have to make do.
> 
> It seems like the obvious thing to do is to continue with aglets1_2; iron
> it
> out and improve it as necessary.
> 
> As for other "versions" of aglets; this is another thing I want to ask
> about. How exactly would we maintain all the different ports of aglets
> effectively? Right now we are having trouble maintaining ports for Java 1
> and 2! Maybe we could keep the "versions" limited to only different aglet
> server implementations. Like a server for Java Micro-Edition or whatever.
> These could then all be in the same codebase. [I'm just throwing this out,
> feel free to object!]
> 
> It would also be nice to have other front-ends for an aglets server --
> like
> a JSP version of the AWT Tahiti (I haven't even looked at the code yet, I
> don't know how hard this would be). Besides JSP, there could be Swing,
> Applet, ... even proprietary ones like COM, KDE2, etc.
> 
> I second the motion of bringing the 1_2 codebase up to speed.
> 
> Daryl.
> 
> 
> 

RE: [Aglets-developer] The Project

[Ferrari, G. D <gre...@lm...>]

I did receive Robert's message, but thanks for the info anyway.  Now that
Aglets is open source there seems to be a few different versions sprouting
in a wild effort to bring it up to date.  I would like to see these verions
combined into one version, managed by the open source folks, that is stable
and provides the ability to make use of all the wonderful features of Java
2.  Once that is accomplished, the open source group can manage the addition
of new platforms.  If things continue the way they are, Aglets will quickly
become just a general name given to a ton of different mobility packages.

> -----Original Message-----
> From:	Daryl Beattie [SMTP:Da...@sc...]
> Sent:	Wednesday, February 14, 2001 1:22 PM
> To:	'agl...@li...'
> Cc:	'Ferrari, Gregory D'
> Subject:	RE: [Aglets-developer] The Project
> 
> Actually, check out Robert's recent posting (which I will quote for you in
> case you hadn't joined the list at that point):
> 
> "There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.
> This
> code has spawned three "releases".  What's referred to as 1.1B3 is the
> aglets1_1 codebase which was the last official release from IBM before
> opening the source.  This code runs on JDK 1.1.8 and is probably the most
> stable version (relatively speaking).  There is another "release" of the
> 1.1
> codebase with modifications to compile under Java 2.  Note, that this is
> /not/ what is in the aglets1_2 codebase.  This version is maintained by
> Kovalan Muniandy at http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/.
> Finally, there is the aglets1_2 codebase which I believe was IBM's next
> version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
> change is that it uses the security features of Java 2 (the keystore for
> example).  This version has some rough edges but it does run. :)"
> 
> Daryl.
> 
> -----Original Message-----
> From: Ferrari, Gregory D [mailto:gre...@lm...]
> Sent: Wednesday, February 14, 2001 12:47 PM
> To: Aglets-Developer (E-mail)
> Subject: RE: [Aglets-developer] The Project
> 
> 
> I have an immediate need for Aglets to run under the latest Java
> technology.
> If I had my way, I would bring Aglets up to the 21st century first (Java
> 2)
> with all its bells and whistles.  Especially Java 2 security features.
> Once
> that is stable, I would start thinking about supporting additional
> platforms
> 
> > -----Original Message-----
> > From:	Robert Bergstrom [SMTP:rbe...@iS...]
> > Sent:	Wednesday, February 14, 2001 11:41 AM
> > To:	Aglets-Developer (E-mail)
> > Subject:	[Aglets-developer] The Project
> > 
> > Hello: 
> > 
> > This is my understanding as to the state of the current codebase.  My
> > information may be incomplete or incorrect, so please contribute
> anything
> > that you know.
> > 
> > There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.
> > This code has spawned three "releases".  What's referred to as 1.1B3 is
> > the aglets1_1 codebase which was the last official release from IBM
> before
> > opening the source.  This code runs on JDK 1.1.8 and is probably the
> most
> > stable version (relatively speaking).  There is another "release" of the
> > 1.1 codebase with modifications to compile under Java 2.  Note, that
> this
> > is /not/ what is in the aglets1_2 codebase.  This version is maintained
> by
> > Kovalan Muniandy at
> <http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/>.
> > Finally, there is the aglets1_2 codebase which I believe was IBM's next
> > version of aglets.  It compiles under Java 2 (I use 1.3), and the
> biggest
> > change is that it uses the security features of Java 2 (the keystore for
> > example).  This version has some rough edges but it does run. :)
> > 
> > That summarizes what I know about the project to date.  The obvious next
> > question is where do we go from here?  There has been some interest in a
> > version of aglets which will run on PDA's.  I'd personally like to see
> the
> > aglets1_2 codebase brought up to speed -- but that's a different post.
> > 
> > Thoughts? 
> > 
> > // RAB 
> > 
> > 
> >   
> > 
> 
> _______________________________________________
> Aglets-developer mailing list
> Agl...@li...
> http://lists.sourceforge.net/lists/listinfo/aglets-developer
> 
> _______________________________________________
> Aglets-developer mailing list
> Agl...@li...
> http://lists.sourceforge.net/lists/listinfo/aglets-developer

RE: [Aglets-developer] The Project

[Daryl B. <Da...@sc...>]

Duh, okay Gregory please ignore my ignorant postings. :P  That's what I get
for reading my e-mails recent-first! Sorry for making a mess of this nice
list already -- I'll control my impulses from now on. :(

I have a question; is it necessary to continue the aglets1_1 code? We can
always keep it around as the "final IBM release"... but it seems to me that
this should be a CVS branch-tagged version, not a separate code-base. But I
suppose we have what we have, and will have to make do.

It seems like the obvious thing to do is to continue with aglets1_2; iron it
out and improve it as necessary.

As for other "versions" of aglets; this is another thing I want to ask
about. How exactly would we maintain all the different ports of aglets
effectively? Right now we are having trouble maintaining ports for Java 1
and 2! Maybe we could keep the "versions" limited to only different aglet
server implementations. Like a server for Java Micro-Edition or whatever.
These could then all be in the same codebase. [I'm just throwing this out,
feel free to object!]

It would also be nice to have other front-ends for an aglets server -- like
a JSP version of the AWT Tahiti (I haven't even looked at the code yet, I
don't know how hard this would be). Besides JSP, there could be Swing,
Applet, ... even proprietary ones like COM, KDE2, etc.

I second the motion of bringing the 1_2 codebase up to speed.

Daryl.


-----Original Message-----
From: Robert Bergstrom [mailto:rbe...@iS...]
Sent: Wednesday, February 14, 2001 11:41 AM
To: Aglets-Developer (E-mail)
Subject: [Aglets-developer] The Project


Hello: 

This is my understanding as to the state of the current codebase.  My
information may be incomplete or incorrect, so please contribute anything
that you know.

There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.  This
code has spawned three "releases".  What's referred to as 1.1B3 is the
aglets1_1 codebase which was the last official release from IBM before
opening the source.  This code runs on JDK 1.1.8 and is probably the most
stable version (relatively speaking).  There is another "release" of the 1.1
codebase with modifications to compile under Java 2.  Note, that this is
/not/ what is in the aglets1_2 codebase.  This version is maintained by
Kovalan Muniandy at http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/.
Finally, there is the aglets1_2 codebase which I believe was IBM's next
version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
change is that it uses the security features of Java 2 (the keystore for
example).  This version has some rough edges but it does run. :)

That summarizes what I know about the project to date.  The obvious next
question is where do we go from here?  There has been some interest in a
version of aglets which will run on PDA's.  I'd personally like to see the
aglets1_2 codebase brought up to speed -- but that's a different post.

Thoughts? 

// RAB 


 

RE: [Aglets-developer] The Project

[Daryl B. <Da...@sc...>]

Actually, check out Robert's recent posting (which I will quote for you in
case you hadn't joined the list at that point):

"There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.  This
code has spawned three "releases".  What's referred to as 1.1B3 is the
aglets1_1 codebase which was the last official release from IBM before
opening the source.  This code runs on JDK 1.1.8 and is probably the most
stable version (relatively speaking).  There is another "release" of the 1.1
codebase with modifications to compile under Java 2.  Note, that this is
/not/ what is in the aglets1_2 codebase.  This version is maintained by
Kovalan Muniandy at http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/.
Finally, there is the aglets1_2 codebase which I believe was IBM's next
version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
change is that it uses the security features of Java 2 (the keystore for
example).  This version has some rough edges but it does run. :)"

Daryl.

-----Original Message-----
From: Ferrari, Gregory D [mailto:gre...@lm...]
Sent: Wednesday, February 14, 2001 12:47 PM
To: Aglets-Developer (E-mail)
Subject: RE: [Aglets-developer] The Project


I have an immediate need for Aglets to run under the latest Java technology.
If I had my way, I would bring Aglets up to the 21st century first (Java 2)
with all its bells and whistles.  Especially Java 2 security features.  Once
that is stable, I would start thinking about supporting additional platforms

> -----Original Message-----
> From:	Robert Bergstrom [SMTP:rbe...@iS...]
> Sent:	Wednesday, February 14, 2001 11:41 AM
> To:	Aglets-Developer (E-mail)
> Subject:	[Aglets-developer] The Project
> 
> Hello: 
> 
> This is my understanding as to the state of the current codebase.  My
> information may be incomplete or incorrect, so please contribute anything
> that you know.
> 
> There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.
> This code has spawned three "releases".  What's referred to as 1.1B3 is
> the aglets1_1 codebase which was the last official release from IBM before
> opening the source.  This code runs on JDK 1.1.8 and is probably the most
> stable version (relatively speaking).  There is another "release" of the
> 1.1 codebase with modifications to compile under Java 2.  Note, that this
> is /not/ what is in the aglets1_2 codebase.  This version is maintained by
> Kovalan Muniandy at <http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/>.
> Finally, there is the aglets1_2 codebase which I believe was IBM's next
> version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
> change is that it uses the security features of Java 2 (the keystore for
> example).  This version has some rough edges but it does run. :)
> 
> That summarizes what I know about the project to date.  The obvious next
> question is where do we go from here?  There has been some interest in a
> version of aglets which will run on PDA's.  I'd personally like to see the
> aglets1_2 codebase brought up to speed -- but that's a different post.
> 
> Thoughts? 
> 
> // RAB 
> 
> 
>   
> 

_______________________________________________
Aglets-developer mailing list
Agl...@li...
http://lists.sourceforge.net/lists/listinfo/aglets-developer

RE: [Aglets-developer] The Project

[Daryl B. <Da...@sc...>]

Dear Gregory,

	Check out http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/1_2/ .
Somebody ported it. I've used it with 1.3 and it works just fine.

Sincerely,

	Daryl.

-----Original Message-----
From: Ferrari, Gregory D [mailto:gre...@lm...]
Sent: Wednesday, February 14, 2001 12:47 PM
To: Aglets-Developer (E-mail)
Subject: RE: [Aglets-developer] The Project


I have an immediate need for Aglets to run under the latest Java technology.
If I had my way, I would bring Aglets up to the 21st century first (Java 2)
with all its bells and whistles.  Especially Java 2 security features.  Once
that is stable, I would start thinking about supporting additional platforms

> -----Original Message-----
> From:	Robert Bergstrom [SMTP:rbe...@iS...]
> Sent:	Wednesday, February 14, 2001 11:41 AM
> To:	Aglets-Developer (E-mail)
> Subject:	[Aglets-developer] The Project
> 
> Hello: 
> 
> This is my understanding as to the state of the current codebase.  My
> information may be incomplete or incorrect, so please contribute anything
> that you know.
> 
> There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.
> This code has spawned three "releases".  What's referred to as 1.1B3 is
> the aglets1_1 codebase which was the last official release from IBM before
> opening the source.  This code runs on JDK 1.1.8 and is probably the most
> stable version (relatively speaking).  There is another "release" of the
> 1.1 codebase with modifications to compile under Java 2.  Note, that this
> is /not/ what is in the aglets1_2 codebase.  This version is maintained by
> Kovalan Muniandy at <http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/>.
> Finally, there is the aglets1_2 codebase which I believe was IBM's next
> version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
> change is that it uses the security features of Java 2 (the keystore for
> example).  This version has some rough edges but it does run. :)
> 
> That summarizes what I know about the project to date.  The obvious next
> question is where do we go from here?  There has been some interest in a
> version of aglets which will run on PDA's.  I'd personally like to see the
> aglets1_2 codebase brought up to speed -- but that's a different post.
> 
> Thoughts? 
> 
> // RAB 
> 
> 
>   
> 

_______________________________________________
Aglets-developer mailing list
Agl...@li...
http://lists.sourceforge.net/lists/listinfo/aglets-developer

RE: [Aglets-developer] The Project

[Ferrari, G. D <gre...@lm...>]

I have an immediate need for Aglets to run under the latest Java technology.
If I had my way, I would bring Aglets up to the 21st century first (Java 2)
with all its bells and whistles.  Especially Java 2 security features.  Once
that is stable, I would start thinking about supporting additional platforms

> -----Original Message-----
> From:	Robert Bergstrom [SMTP:rbe...@iS...]
> Sent:	Wednesday, February 14, 2001 11:41 AM
> To:	Aglets-Developer (E-mail)
> Subject:	[Aglets-developer] The Project
> 
> Hello: 
> 
> This is my understanding as to the state of the current codebase.  My
> information may be incomplete or incorrect, so please contribute anything
> that you know.
> 
> There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.
> This code has spawned three "releases".  What's referred to as 1.1B3 is
> the aglets1_1 codebase which was the last official release from IBM before
> opening the source.  This code runs on JDK 1.1.8 and is probably the most
> stable version (relatively speaking).  There is another "release" of the
> 1.1 codebase with modifications to compile under Java 2.  Note, that this
> is /not/ what is in the aglets1_2 codebase.  This version is maintained by
> Kovalan Muniandy at <http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/>.
> Finally, there is the aglets1_2 codebase which I believe was IBM's next
> version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
> change is that it uses the security features of Java 2 (the keystore for
> example).  This version has some rough edges but it does run. :)
> 
> That summarizes what I know about the project to date.  The obvious next
> question is where do we go from here?  There has been some interest in a
> version of aglets which will run on PDA's.  I'd personally like to see the
> aglets1_2 codebase brought up to speed -- but that's a different post.
> 
> Thoughts? 
> 
> // RAB 
> 
> 
>   
> 

[Aglets-developer] The Project

[Robert B. <rbe...@iS...>]

Hello:

This is my understanding as to the state of the current codebase.  My
information may be incomplete or incorrect, so please contribute anything
that you know.

There are two versions of the ASDK in CVS -- aglets1_1 and aglets1_2.  This
code has spawned three "releases".  What's referred to as 1.1B3 is the
aglets1_1 codebase which was the last official release from IBM before
opening the source.  This code runs on JDK 1.1.8 and is probably the most
stable version (relatively speaking).  There is another "release" of the 1.1
codebase with modifications to compile under Java 2.  Note, that this is
/not/ what is in the aglets1_2 codebase.  This version is maintained by
Kovalan Muniandy at http://www.cis.ohio-state.edu/~muniandy/agletsd-j2/.
Finally, there is the aglets1_2 codebase which I believe was IBM's next
version of aglets.  It compiles under Java 2 (I use 1.3), and the biggest
change is that it uses the security features of Java 2 (the keystore for
example).  This version has some rough edges but it does run. :)

That summarizes what I know about the project to date.  The obvious next
question is where do we go from here?  There has been some interest in a
version of aglets which will run on PDA's.  I'd personally like to see the
aglets1_2 codebase brought up to speed -- but that's a different post.

Thoughts?

// RAB


 

RE: [Aglets-developer] aglets.org

[Robert B. <rbe...@iS...>]

Yes, I've had that happen as well.  I believe "luckspin" was running it.  I
have admin on the sourceforge site, but not the aglets.org site.  I'll email
him and see if something can be done.

// RAB
a.k.a. Kbd4Hire

-----Original Message-----
From: Daryl Beattie [mailto:Da...@sc...]
Sent: Tuesday, February 13, 2001 5:55 PM
To: 'agl...@li...'
Subject: [Aglets-developer] aglets.org


Dear Aglet developers,

        I e-mailed the st...@ag..., and my message was bounced back to
me... So, I don't know where else to look for people that would be able to
release some control over this site. Any insight would help.

[Aglets-developer] aglets.org

[Daryl B. <Da...@sc...>]

Dear Aglet developers,
 
        I e-mailed the  <mailto:st...@ag...> st...@ag..., and my
message was bounced back to me... So, I don't know where else to look for
people that would be able to release some control over this site. Any
insight would help.
 
Sincerely,
 
        Daryl.
 

Daryl Beattie
Java Developer/Research and Development
ScreamingMedia
601 West 26 Street 13 Floor
New York New York 10001
T 212 691 7900 F 212 691 1483
Direct 212 659 1895
www.screamingmedia.com <http://www.screamingmedia.com/>  


 <http://www.screamingmedia.com/> ScreamingMedia

ScreamingMedia makes  <http://www.screamingmedia.com/en/press/> headlines