headers
Nic Ferrier | 21 Nov 2003 09:55
Picon

Another reason why XSLT uses XML syntax

While out with the dog on a rainy night I thought of the obvious
reason why XSLT is in XML syntax (I think this is one of the official
design reasons, it's just that I forgot it).

It's in XML because it generates XML. It means the language is
simpler to implement because, as an implementor, you don't need to
implement the XML infospec and validation rules... an XML parser does
it for you.

When the XSLT engine sees an XSLT script it can gaurantee that it is
well-formed (otherwise the parser would have complained about loading
it). That's half the battle with a complex template language.

The XML syntax also allows namespaces and all that guff to be
specified in a naturalistic way.

So, even thought it sucks from an authors point of view, there is a
good reason for it.

Btw I've always thought that XML syntax was pretty poor for
authors. Whenever I write anything substantial I use GNU's Texinfo
format and then convert it to XML (there are tools for that).

Texinfo is a markup language inspired by TeX and it's much easier to
write lots of than XML is.

Nic

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
(Continue reading)

Permalink | Reply | 0 comments |
headers
Steven J. Owens | 26 Nov 2003 07:03

JSP/Servlets Software Architect Salaries?

Hi guys,

     Anybody have a handy job description and salary range for a
JSP/Servlets "software architect"?

     I'm negotiating with a startup I'm working on with some folks.
To make a long story short, we're talking about setting up a "some
cash/some stock" compensation plan.  Basically the plan is to be that
each person gets paid a fraction of a fair market rate in cash (so we
don't starve) and the remainder in stock.

     The CEO came up with what I consider a low number that he got
from payscale.com, for a "senior software engineer".  The thing is,
I'm the only geek on this project. The CEO and I thrash out the market
requirements on a constant basis (which have shifted over the course
of the year we've been working on this), I implement, test, deploy,
and administrate.

     Mind you, the software isn't rocket science.  In fact it's pretty
boilerplate, JSPs and servlets and simple javabeans.  The only
challenging part has been keeping the code agile enough to respond to
changing requirements, which I've pretty much done.

     Still, I'm not just slinging code here, I'm pretty much solely
responsible for putting this whole thing together.  So I feel that
perhaps a salary rate for a "senior software developer", estimated
based on corporate salaries where said developer is part of a team, is
not appropriate.  Software architect is becoming a popular buzzword,
and it seems to mean "responsible for the larger design of the
project".  If anybody has recommendations for other titles to examine
(Continue reading)

Permalink | Reply | 2 comments |
headers
Arnaud | 26 Nov 2003 08:49
Picon
Favicon

Re: JSP/Servlets Software Architect Salaries?

Well, it depends also on your location. My salary
almost doubled between France and Switzerland, but
cost of living differ (not to mention insurances,
health care, and what not), so a 100% increase in
salary actually became a 20% increase in standard of
living. I hear east coast and west coast salaries in
the US differ as well.

 --- "Steven J. Owens" <puffmail <at> darksleep.com> a
écrit : > Hi guys,
> 
>      Anybody have a handy job description and salary
> range for a
> JSP/Servlets "software architect"?
> 
>      I'm negotiating with a startup I'm working on
> with some folks.
> To make a long story short, we're talking about
> setting up a "some
> cash/some stock" compensation plan.  Basically the
> plan is to be that
> each person gets paid a fraction of a fair market
> rate in cash (so we
> don't starve) and the remainder in stock.
> 
>      The CEO came up with what I consider a low
> number that he got
> from payscale.com, for a "senior software engineer".
>  The thing is,
> I'm the only geek on this project. The CEO and I
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nic Ferrier | 26 Nov 2003 09:13
Picon

Re: JSP/Servlets Software Architect Salaries?

"Steven J. Owens" <puffmail <at> darksleep.com> writes:

> Hi guys,
> 
>      Anybody have a handy job description and salary range for a
> JSP/Servlets "software architect"?
> 
>      I'm negotiating with a startup I'm working on with some folks.
> To make a long story short, we're talking about setting up a "some
> cash/some stock" compensation plan.  Basically the plan is to be that
> each person gets paid a fraction of a fair market rate in cash (so we
> don't starve) and the remainder in stock.
> 
>      The CEO came up with what I consider a low number that he got
> from payscale.com, for a "senior software engineer".  The thing is,
> I'm the only geek on this project. The CEO and I thrash out the market
> requirements on a constant basis (which have shifted over the course
> of the year we've been working on this), I implement, test, deploy,
> and administrate.
> 
>      Mind you, the software isn't rocket science.  In fact it's pretty
> boilerplate, JSPs and servlets and simple javabeans.  The only
> challenging part has been keeping the code agile enough to respond to
> changing requirements, which I've pretty much done.
> 
>      Still, I'm not just slinging code here, I'm pretty much solely
> responsible for putting this whole thing together.  So I feel that
> perhaps a salary rate for a "senior software developer", estimated
> based on corporate salaries where said developer is part of a team, is
> not appropriate.  Software architect is becoming a popular buzzword,
(Continue reading)

Permalink | Reply | 0 comments |
headers
vorutidaku2708 | 26 Nov 2003 18:05
Picon
Favicon

I found this site in another group I belond to

This site was recently launch. Seems like a good idea, since there 
are so many online dating sites:

http://www.reviewonlinedating.com

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/saFolB/TM
---------------------------------------------------------------------~->

Before posting a question, try to find your answer here: 
<http://www.egroups.com/links/advanced-servlets>
Announcements should go to: advanced-servlets-announce <at> egroups.com
To Post a message, send it to: advanced-servlets <at> eGroups.com
To Unsubscribe, send a blank message to: advanced-servlets-unsubscribe <at> eGroups.com 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Permalink | Reply | 0 comments |
headers
Steven J. Owens | 30 Nov 2003 02:35

Http Request Queue

Hi all,

     I'm thinking about building a generic mechanism in this project,
to hold HTTP requests in a database table.

     I have some pieces of the system that post stuff out, and get
results posted back.  Right now we have the *very* low-tech approach.
The response post just generates an email and somebody handles it from
there, reviewing the results and clicking the right buttons to start
the next action in the chain.

     I don't want to lock it down to a specific set of parameters,
because this thing will shift over time, as it already has been
shifting.

     In the spirit of refactoring, I'm thinking the next small step
would be to just have the post go into a table and wait there, and
then I can display the results in a form that suggests the right
buttons.

     So there's the easy way, the right way, and the brute force way.

     The easy way is to just store the mime-encoded text in a single
database column.  Except that the servlet engine doesn't give me the
mime-encoded version, so I basically have to reconstitute it.  Then to
pull it out, I have to re-parse the mime-encoded text.  So okay,
that's not so easy.

     The right way is to have four tables:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Greg Wilkins | 30 Nov 2003 07:02
Gravatar

Re: Http Request Queue


I don't think you should be storing the HTTP Request in your DB, as
I see no reason for you to store all the protocol stuff and encodings etc.
in the DB.

Surely you just want to store the parameters (and perhaps URL) in the
DB?   You could do this either with a name/value table or you could
build a java object to represent the request (semantically) and then
store that object as a single blob in a single row/column of the DB.

Note that serializing the request object is not going to work.
I doubt it would serialize in most containers and even if it did, the
spec says that a request is not valid outside of it's calling scope.
Thus that approach would just not be portable.

regards

Steven J. Owens wrote:
> Hi all,
> 
>      I'm thinking about building a generic mechanism in this project,
> to hold HTTP requests in a database table.
> 
>      I have some pieces of the system that post stuff out, and get
> results posted back.  Right now we have the *very* low-tech approach.
> The response post just generates an email and somebody handles it from
> there, reviewing the results and clicking the right buttons to start
> the next action in the chain.
> 
>      I don't want to lock it down to a specific set of parameters,
(Continue reading)

Permalink | Reply | 0 comments |
headers
David M. Lehrian | 30 Nov 2003 07:48

Re: Http Request Queue

Hi Steve,
I would think that the answer would be dictated by the use of the database.  If you need to select HTTP requests
based on the individual parameter values, then putting them into name/value fields makes sense.  If you
are simply storing them and processing them based on a time stamp, I would think that you could store the
request as a string in a single field and parse is when it comes out.  Or, like another person mentioned,
parse it up front into an object and then store the object.  The only reason the deal with splitting it out
IMHO is to select on the data.  Splitting them out does create a data integrity issue to be managed, not that
big of a deal, but it is a consideration. 
Warm Regards,
Dave

_______________________________________________
David M. Lehrian
Software Engineer
    831-761-8662
    5022 Royal Oak Place
    Royal Oaks, CA 95076-9000
http://www.salinasofficesolutions.com/
http://www.easypetidtags.com/
http://www.redshift.com/~lehrian
_______________________________________________
  ----- Original Message ----- 
  From: Steven J. Owens 
  To: advanced-servlets <at> yahoogroups.com 
  Sent: Saturday, November 29, 2003 5:35 PM
  Subject: [advanced-servlets] Http Request Queue

  Hi all,

       I'm thinking about building a generic mechanism in this project,
(Continue reading)

Permalink | Reply | 0 comments |

Gmane